It's not memory leaks, it's memory clings. [Jforum] J Server sessions cling on memory http://www.jsoftware.com/pipermail/general/2005-January/019954.html
> In general (even in Windows) it would probably be better to do the Jinit > only once in an application and then use normal J facilities (4!:55 etc) If only one J instance per process were needed, it's OK without saying. The problem is when you need multiple short-lived instances. An example is IIS (ASP) application which for every page creates a J instance. The only known workaround is in the quoted message. It looks like there are no private heaps provided by UNIX. It's up to application libraries, e.g. auto release pools in Objective-C. --- Eric Iverson <[EMAIL PROTECTED]> wrote: > JFree doesn't work (is just a noop) in unix. > > In windows all J memory allocation is done in a J heap and JFree > destroys that heap. This is dead simple, almost guaranteed to be > complete, and relatively safe. > > When the Unix shared library J Engine was added in for 601it wasn't > clear how to achieve this in Unix. There didn't seem to be an equivalent > service that made it as easy as it was in Windows. > > In general (even in Windows) it would probably be better to do the Jinit > only once in an application and then use normal J facilities (4!:55 etc) > to free J memory as desired. > > Apolgies that the lack of documentation on this wasted some of your > time. > > Adavance warning: JClear doesn't work in either Windows or Unix. JClear > uses 4!:56 to erase all J allocations and 4!:56 was removed as there > were complications in the implementation. > ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
