@lax Build 4456 CTDs .Net Apps

rootkit · Post by **rootkit** » Sat May 26, 2007 6:10 am

With the latest IS build all my .Net Apps crash to desktop right after I stop the main thread aka quit the program.
Already compiled my sources against the new dlls, no problems at all.

rootkit · Post by **rootkit** » Mon May 28, 2007 6:05 am

Ok, found a workaround. Put in a Frame Lock before terminating the main thread.

Post by **Lax** » Mon May 28, 2007 9:56 am

My apps work fine, you might consider debugging your app?

stardog · Post by **stardog** » Mon May 28, 2007 4:13 pm

This worked for me .... WOOOt thanks for the tip.

Lax, its something with IsDisposed(). or something
the only one of my apps that crashes is the one that has a seperate form that had a timer on it with an event that triggeered every 1 second to update a display. and when i closed the form, it was still trying to access an object that wasn't there.. I finaly got the debugger to not catch any mor exceptions no matter how hard i tried. but Would still crash to the desktop after killing my main thread (like the above poster).
Im a totaly newb so it very well could be my code. but that fix worked for me.. and it only started with the latest patch.
PS: i am also calling Threads with the invooke method.
via
this.Invoke(new UpdateTextHandler(UpdateOpenSlotsLabelText), new object[1] { openslots });

Anyhow, i can get more data if you like, it very well could be my code.
buts its working now so .. i'm off like a prom dress

stardog · Post by **stardog** » Tue May 29, 2007 12:39 pm

I think i can explain this better.
in suedo terms.

If you close a form, it seems that there may still be threads in Inner space Qued up , and when you close the form, and inner space sends them back to the form (or something like that ) that there is no more valid control and it crashes. I could not get anything in the debugger to pick up on it. and all my lavish crashes were dotnet related, however. The frame.Lock() call in the close function of my Main thread fixed it.. No crashes.
I was able to repeat it every time. and i have now went over 60 closes with Zero crashes.

I don't think its an innere space or .net thing, but Some by product of both.
Then again. i have no clue what 'im talking about

rootkit · Post by **rootkit** » Tue May 29, 2007 2:28 pm

Already debugged my stuff. It doesnt crash on my managed code. I dont even think that it crashes on ur managed code, u know, the code that gets executed after my main loop has stopped. I think it crashes in ur unmanaged code.

psogaa · Post by **psogaa** » Wed May 30, 2007 4:15 pm

rootkit wrote:Ok, found a workaround. Put in a Frame Lock before terminating the main thread.

Thank you, thank you, thank you

Was having the same problem myself, but only got as far as trying to add a Frame.Lock() on my form closing event.
Your workaround seems to do the trick though

psogaa · Post by **psogaa** » Wed May 30, 2007 4:16 pm

psogaa wrote:...but only got as far as trying to add a Frame.Lock() on my form closing event....

Meant Frame.Unlock() ofcourse (there's no edit button on this forum?)