Debugging an applet - lost for solutions

[olbion]

I have an applet which sometimes freezes and I'm trying to find out why.

In Linux, I've located the problem to disabling a button. More precisely, Canvas.setEnabled(false). If I comment that out, the applet runs ok (but the button is still active of course, which it is not supposed to be).

When I run the same applet in Internet Explorer, it freezes anyhow, whether or not the button is disabled. The applet window freezes, as does the console (to which no error message is written) and the browser.

In no case does the CPU usage go up, so it does not seem to be an infinite loop that is causing the problem.

I'm somewhat lost as to how I can continue debugging this applet. Any suggestions? Any ideas that could point me in a constructive direction are very welcome!

[sukatoa]

I hope you didn't initialize the GUI on paint(method)... sometimes, others don't care about it. It should be used for Draw or to print some text.

can you show as the pseudocode of your program?

[olbion]

Hi,

Thank you for your answer. Do you mean whether the applet main class makes use of the "paint(Graphics g)" method? If so, the answer is no.

I've managed to isolate the problem further. What happens is this:

An event is sent from a server to the java applet/client. Among these, a button is disabled, and a html string is read into a JEditorPane. I've discovered that commenting ONE of these actions out, the applet runs fine. That is, it can either disable the button OR read the string into the JEditorPane, but not both - then it freezes. The offending code lines are:

EditorKit kit = getEditorKit();
StringReader reader = new StringReader(html);
Document doc = getDocument();
kit.read(reader, doc, doc.getLength()); //A

-------------------

Canvas.setEnabled(false) //B

I have to comment out either (A) or (B). If both (A) and (B) are active, then the applet freezes, when executing (B). If one or both are commented out, the applet runs fine.

Any ideas? All help very much appreciated!