MaxGUI Mac OS X - Threads

Archives Forums/MaxGUI Bug Reports/MaxGUI Mac OS X - Threads

Phlox(Posted 2010) [#1]
Hi,

I think these are quite interesting bugs in MaxGUI..

1.: When using threads on Mac OS X and they do certain things like interacting with MaxGUI or some other things, the 'output' shows me lots of Warnings like these:

08.11.10 18:07:59 RoBoTNatalius[1303] *** __NSAutoreleaseNoPool(): Object 0x1ab0b140 of class NSSelectionArray autoreleased with no pool in place - just leaking
08.11.10 18:07:59 RoBoTNatalius[1303] *** __NSAutoreleaseNoPool(): Object 0x1ab0b620 of class NSSelectionArray autoreleased with no pool in place - just leaking
08.11.10 18:07:59 RoBoTNatalius[1303] *** __NSAutoreleaseNoPool(): Object 0x6f3280 of class NSConcreteValue autoreleased with no pool in place - just leaking
08.11.10 18:07:59 RoBoTNatalius[1303] *** __NSAutoreleaseNoPool(): Object 0x1ab06090 of class NSCFDictionary autoreleased with no pool in place - just leaking
08.11.10 18:07:59 RoBoTNatalius[1303] *** __NSAutoreleaseNoPool(): Object 0x1aa07650 of class NSSelectionArray autoreleased with no pool in place - just leaking


And when the program ends, MaxIDE sais: Compile Error and then one of these messages. This is very bad, because after a few seconds, the Mac OS X console is full and takes up much space on the harddrive.

2.: The Apps run VERY instable when using threaded Build, one click in a canvas or on a panel can make them freeze and crash.

3.: The problem is, that this does not happen on Windows, BUT there the Splitter-ProxyGadgets are dragged even without a click when on a panel (why??)...


I am running Mac OS X 10.6.5 and BlitzMax 1.41. With the beta of the new MaxGUI it runs EVEN WORSE, because it does not update always.


I hope you can help me, this project is very important to me.


Christian F. Coors


SebHoll(Posted 2010) [#2]
MaxGUI is not thread-safe and so you should only call MaxGUI commands from the main thread.