Known Bugs and Limitations
OmniObjectAlloc is BETA software at this point. We are releasing it to get some feedback on how well it works and since it seems like a very useful tool that may help some people fix their memory problems. But, OOA still has many shortcomings. Here are some of them. Please send bug reports to ooa@omnigroup.com if you don't see them here.
- The 'Stop' button on the document panel does nothing. It simply isn't implemented yet.
- Multiple document support isn't tested yet. This includes closing and reopening the same document. This, together with the previous bug means that each time you want to run your app, you'll probably have to restart OOA.
- OOA still leaks. Not as bad as it used to, but it isn't leak free by any means.
- OOA exposes some weird bugs in OpenStep/4.2 and the Rhapsody kernels. If you are debugging OOA, launch the client app and then quit OOA without quiting the client application, often the system time will skyrocket. This isn't that bad since it seems to give way to user processes. The real problem comes about when you try to reboot the machine. It will hang.
- I haven't bothered to make the menu on the Rhapsody version conform to the proper standards for that platform yet. I do the majority of my development on OpenStep/4.2 currently so that version of the main nib gets more updating than the Rhapsody version.
- The 'Find' panel is currently broken due to other changes. This isn't hugely critical functionality since you can generally find objects yourself. It will get fixed though since there are some cases in which you don't know the class of the object (and thus, you can't easily find the object).