I had the same question. In all of the years I've worked with Java I've always thought it was free of memory leaks. If you use a different compiler does the problem go away. Is that how people like JRun (Macromedia) and WebSphere (IBM) avoid the problem?
Which bug are you talking about, the classloader reload memory leak or the javac memory leak? The latter, they probably just fork javac by default. The former, well, I'd like to see whether or not they do suffer from that issue or not!
-Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
