destroy()/stop() in applets

Hello,

I am having very serius problems with a web application. The problem is, the applet does not close properly upon any of the following operations: reload, back/forward page and in some cases even when I close the entire broswer. After pressing reload so many times; there is a heap overflow that is created because the applet has loaded so many instances of itself. I have overidden both the stop() and destroy() methods and they join() all open threads, problem is; it looks like these methods are never actually called. I can't find any reports of any problem like this; so I was wondering if anyone could give me a more detailed explanation of how to "properly" make a applet stop/destroy its resources. Oh; one last side note; this has been tested on many computer with the same result.

Thanks a lot,

Bobby

[842 byte] By [panthara] at [2007-10-3 4:26:53]
# 1

It sounds to me like the browser is buggy. It should be calling those methods.

Anyway it should be easy to check if the methods are being called. Just have them write trace statemtns to System.err or System.out. They should show up in the java console. (Unless the browser doesn't have one, in which case you really have a problem.)

What browser is this?

paulcwa at 2007-7-14 22:29:35 > top of Java-index,Desktop,Core GUI APIs...