DX2 Crashing

Can someone try this and see if it's a DX2 bug?

Select numerous scripted objects...does DX crash?

Here is a screenshot of what I mean...



I had posted this in the Neowin DX board, and got a reply from Frogboy asking me to mail the DesktopX.dmp file...which I did. This was almost a month ago and 2 new beta's have been released since. So now I'm not sure if it's just me or they just haven't gotten around to fixing this DX bug. Does it happen to you too?
5,391 views 15 replies
Reply #1 Top
Hus - does this just pop up anytime or is it after you do or start something else...?

BTW: what's that 'blue' thing in the screenshot?



Powered by SkinBrowser!
[Message Edited]
Reply #2 Top
When I drag a select box around multiple objects. DX will crash EVERY TIME. That 'blue' thing is the select box...I dunno the proper name...without DX it's a clear white box? The only other times DX crashes is when I'm tinkering...so it's expected. This happens 100% of the time and it gets annoying, if I want to move objects, I have to do it one by one...I cant select them all...
Reply #3 Top
The 'select box' is a new one...but I'll play with that one and see what happens. As far as moving all the objects, yes, that's a bug. If I lock or unlock all in config. DX will usually crash. If I do one at a time I have no problems. You might disable error reporting altogether and see if you get a script fault so that, at least you'll know which object it is and go from there.



Powered by SkinBrowser!
Reply #4 Top
What do you mean by 'lock or unlock all'? Also, it happens with any object...Stardock Certified...anything, so I doubt it's a script issue...
Reply #5 Top
In DX config under Desktopx tab/default movement: locked - unlocked. I found it doesn't matter whether it's certified or not, some objects just have problems on some systems...it's like anything else...if there's 50 million systems, that's 50 million different systems running 50 million different apps. If you don't think it's a script thing then look at what else is running and take them down one at a time until you find the crasher...just might not be DX.



Powered by SkinBrowser!
Reply #6 Top


I stripped all running proccesses except for generic system processes and DX. Still crashed.
Reply #7 Top
Well, that answered that question! I've tried just about every type of object...exactly which ones are you running?



Powered by SkinBrowser!
Reply #8 Top
Right now, I have a CPU, RAM and Net In/Out meters, a calendar and a text uptime. IconX is enabled...
Reply #9 Top
Disable Icon-X



Powered by SkinBrowser!
Reply #10 Top
Ok! We're making progress here!

I would of never thought IconX would interfere with an object? But sure enough, it doesn't crash with IconX disabled. Friggin' wierd! Also, if I select 10 IconX icons, it wouldn't crash...only when I selected objects. Well...it's not fixed...but atleast we found the problem! I'm gonna call you 'The All-Seeing yrag'.
Reply #11 Top




Powered by SkinBrowser!
Reply #12 Top
Well, 1st part out the way...just one more thing...does this happen to you too? Enable IconX, and select multiple scripted objects. Crashes?
Reply #13 Top
Yeah...I don't use any desktop icons thus IconX is disabled, but I've enabled before (usually when a new built comes up) just to see if there's any problems and so far it has never played well with scripted objects. I've posted it in the newsgroups and they're aware there is a problem...just have to grin and bear it until they fix it.........I'm sure they'll get a handle on it

BTW: nice desktop



Powered by SkinBrowser!
[Message Edited]
Reply #14 Top
Ok cool, thanks very much for your help yrag! Er.."All-Seeing yrag! "
Reply #15 Top
No problem ....and keep that Popcorn coming....



Powered by SkinBrowser!