One thing to look for is if you are running in threads, that every thread should have its own autorelease pool being set up before doing anything.
Alan Third wrote on 27.04.22 22:08: > I'm investigating some memory that have been reported in the GNUstep > port of Emacs. The reporter says they're getting warnings in the > console about objects being autoreleased when there is no autorelease > pool. > > Now, I'm pretty sure I know what's causing that particular problem, > but I don't see these warnings so I can't be sure. Even if I > intentionally break our autorelease pools I get nothing and I can't > work out what I need to do to enable these messages. > > I suspect the difference is that they're using gcc and I'm using > clang. I built my own GNUstep install using some instructions I can't > find now. > > Any pointers that would help me debug this would be appreciated. > > Thanks!
