DrumsArt

Unhandled Exception

Recommended Posts

Hi,

During approach I had an Unhandled Exception "Object is currently in use elsewhere" !

Fsx Acc, P2Atc last update.

2017-4-29_16-9-32-486_zpsghlwrpgx.jpg

Thanks and Regards,

Richard Portier

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Thanks for the report Richard.

This is a Windows error when the Graphics object is trying to be used by multiple programs to paint the screen or controls. 

Did you have the AI Traffic visible at the time?  That sometimes causes this.

Did it keep running OK when you pressed Continue?

Thanks,

Dave

Share this post


Link to post
Share on other sites
3 hours ago, Dave-Pilot2ATC said:

Thanks for the report Richard.

This is a Windows error when the Graphics object is trying to be used by multiple programs to paint the screen or controls. 

Did you have the AI Traffic visible at the time?  That sometimes causes this.

Did it keep running OK when you pressed Continue?

Thanks,

Dave

Dave, if you speak about the AI traffic visible IN P2Atc, the answer is yes ! I have not pressed "Continue", so...

Regards,

Richard

Share this post


Link to post
Share on other sites

Richard

Usually, with this particular issue, you can press Continue and all will continue to function.  Key word is "Usually".

Thanks,

Dave

Share this post


Link to post
Share on other sites

Dave, this looks really really fishy... No sane API would produce such an exception unless something is wrong somewhere within the program itself. I'm a professional programmer myself and this looks like actual programmer's error to me. I googled for this kind of exception and found several possible explanations, most of which revolved around doing graphics-related operations in threads, when given operation is not thread-safe (one such example was Bitmap-related). Also, in general, doing any UI-related operations in non-UI thread was pointed as a culprit. And of course we don't see it all the time with Pilot2ATC, because that's the nature of threading-related issues or race conditions...

Any chance you can look at the issue from this perspective? I experienced this exception one or two times too (I think I sent it over to you the other day, not 100% sure as it was one of a few other issues I reported).

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now