Why does MSIE6 crash on Windows2000 server when re-loading!_NEWLINE_!awt applet ?
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Archana_Jayaswal
Posted On:   Friday, January 25, 2002 12:50 PM

After reloading the applet page a couple of times ( the number of times it loads successfully varies!!!)in MSIE6.0 on Windows2000, the browser crashes ( we see black patches where the applet is supposed to be). - Java Console freezes too, but debug printlines indicate that when the crash occurred the applet's init() method was not called.. - destroy() and init() are called each time the applet was successfully reloaded. - If the contents of the entire init method was commented out, it did not seem to crash.... As expected, there was just a grey background on the browser in place of the applet, for this particular case. - This is an aw   More>>

After reloading the applet page a couple of times ( the number
of times it loads successfully varies!!!)in MSIE6.0 on Windows2000,
the browser crashes ( we see black patches where the applet is supposed
to be).


- Java Console freezes too, but debug printlines indicate
that when the crash occurred the applet's init() method was
not called..
- destroy() and init() are called each time the applet was
successfully reloaded.


- If the contents of the entire init method was commented
out, it did not seem to crash.... As expected, there was just a
grey background on the browser in place of the applet, for
this particular case.
- This is an awt applet, which extends another applet
class, and used to work on NT, with IE browsers before version4


I suspect memory leaks because of the variable nature of the
crash.. but do not know how to fix it or investigate it further.
How do I know why MSIE and applet crashed?? How do I fix
this problem ?Are there any log files I should be looking at to
get some clues?
Thanks a lot for your help!!

   <<Less

Re: Why does MSIE6 crash on Windows2000 server when re-loading!_NEWLINE_!awt applet ?

Posted By:   Badis_BenHamida  
Posted On:   Friday, January 25, 2002 01:56 PM

it is hard to tell without looking at the applet but I had a similar problem before that turned out to be associated with a thread not cleaned-up everytime the applet quits and reloads. Open the Java console and press "t" everytime you reload the applet. keep track of the number of threads make sure it is not increasing. hope this helps.
About | Sitemap | Contact