ContextSwitchDeadlock /COM MDA erros with latest release

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

While debugging, I get various errors, like "ContextSwitchDeadlock" and some kind of COM disconnect error. I'm not sure how these show when not debugging, but so far I have not been able to burn an audio disc successfully in debug mode. Could you please check if that can be fixed?

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Hello,

Thanx, Checking...

Dmitry

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

I believe that in non-debug mode, it sometimes causes the application to hang (forever) after inserting a new disc. Maybe there is a problem with thread safety that needs to be addressed. I can reproduce that quite reliably on my own computer. Let me know what details you need to fix that issue.

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Hello,

At the first we should reproduce this error here!

Regards,

Dmitry

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

OK. At one occasion, it hanged when accessing Device.DiscInfo.DiscType of a drive in the UI thread, after calling Drive.DiscInfo.Refresh() in a background thread.

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Ok! THANX!!!

Dmitry

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

Did you find anything in regard to this issue? Can I do something to help you?

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Hello,

Yes, I guess we have found source of this problem! We will fix it in the next build!

What you can do right now to fix this issue ... you should cache the DiscInfo object for the UI thread and call all methods directly on this object!!

Regards,

Dmitry

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

That's great

I guess I won't create an artificial workarounds for now since not that many users are complaining, but I'd appreciate a timely update.

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

In regard to these strange issues: This release also appears to prevent my app from shutting down correctly on Windows XP. On Windows 7 it exits properly, but when run on Windows XP, when the list of drives has been loaded, the process does not exit after all windows has been closed. Any ideas?

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

flöle wrote:

In regard to these strange issues: This release also appears to prevent my app from shutting down correctly on Windows XP. On Windows 7 it exits properly, but when run on Windows XP, when the list of drives has been loaded, the process does not exit after all windows has been closed. Any ideas?

To provide a bit more detail: It does no longer shut down as soon as an ImageBurner-object has been created. Even running a Marshal.ReleaseComObject() on the created object does not make the application exit. Creating a DVDVideoBurner or AudioBurner instead does not cause the issue. So I would guess that is something you need to look into.

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Hmm ... interesting ...

We will check it! Many thanx!

Dmitry

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

Any new release in sight yet?

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Hello,

The new version ( v.13 ) is released, could you check your issue with new version?

Regards,

Dmitry

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

Currently trying, but didn't get very far. Whenever I call the UDFDataBurnerClass.GetFileObject() method, I get an exception if the object to find does not exist, instead of a null return value: 0x800402AA

Log attached.

And MDAs are not gone yet: http://www.starburnsoftware.com/forum/post12776.html#p12776

#1 Burning Software

ContextSwitchDeadlock /COM MDA erros with latest release

Who is online