8 replies to this topic

[Alodielle]

Been receiving this error since last night:

Traceback (most recent call last):
File "/cdx/svn/checkout/core/trunk/Program Manager/ProgramManager.py", line 1306, in run_with_except_hook
File "Programs/1001/Abrosia.py.nc", line 41, in run
File "wx\_core.pyc", line 14610, in __getattr__
PyDeadObjectError: The C++ part of the ProgramFrame object has been deleted, attribute access no longer allowed.

Thoughts?

[Waser Lave]

Does it happen after you close the program?

[ElBastardoVerde]

Yes, it happens when you close the program or hit the 'Stop' button.

[Alodielle]

The program appears to freeze in its operations -- it'll get stuck on "Visiting _____ Shop" and not move. Then, when you hit "Stop" or close the program, the error pops up.

[krakus]

Just adding that this has been happening to me a lot recently. Whenever I stop the program or close it, I come up with this error.

[ShadowLink64]

Fixed.

The problem occurred in two different scenarios (if anyone wants the technical mumbo jumbo):

• Main program thread crashes, but doesn't close the secondary timer threads (which update the status bar). When the entire program is aborted, this thread tries updating a non-existent status bar...
• Program is closed without pushing the Stop button: In this case, all threads are still active in the background trying to update a non-existent status bar.

Now upon closure, Abrosia checks the status of all running threads and aborts them before closing the program window. This error may still pop up under some rare circumstances (ie. where the main thread cannot close in time during a buy or something very long).

[Alodielle]

Thank you.

[Alodielle]

So... this has started back up again....