[Please take out [email protected] when replying. Or is there a better way?]
Am Donnerstag, den 30.09.2010, 09:54 -0400 schrieb Andres Cimmarusti: > > The behaviour is still the same as when I last commented on the bug. > > Trying an applet like > > http://java.sun.com/applets/jdk/1.4/demo/applets/Clock/example1.html > > will still make the browser unresponsive - the applet runs, but the rest > > of the browser is unusable. > > Same here. I had kill the process because it ramped the cpu usage to > 100% and browser was completely unusable. My arch is amd64 Alright, but the original report is about something else. So I would suggest to close this report and open a new one with the correct tags set. Maybe your bug is the same as #594470 [1]? Thanks, Paul PS: The maintainer seems to be quiet busy, so I guess it will help him to be as clear as possible with all the reports. (Sven already helps a lot with Debian bug reports as far as I could see. Thanks, Sven!) [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594470
signature.asc
Description: This is a digitally signed message part
