openjdk team mailing list archive

[TJ <ubuntu@xxxxxxxxxxx>]

I was able to catch the Volano chat (see spunkyworld chat demo) running
at 100% with gdb. It seems to show one thread is corrupted in some way.
Using 'top' with option 'H' (show threads) I got the LWP process ID of
the thread. In gdb I checked that with "info threads" then switched to
the thread "thread 11" and tried to get a backtrace.

(gdb) info threads
  24 Thread 0xb77afb70 (LWP 10790)  0x00cc7422 in __kernel_vsyscall ()
  23 Thread 0x8c463b70 (LWP 10792)  0x00cc7422 in __kernel_vsyscall ()
  22 Thread 0x8c3e2b70 (LWP 10794)  0x00cc7422 in __kernel_vsyscall ()
  21 Thread 0x8c19cb70 (LWP 10796)  0x00cc7422 in __kernel_vsyscall ()
  20 Thread 0x8c11bb70 (LWP 10798)  0x00cc7422 in __kernel_vsyscall ()
  19 Thread 0x8c0cab70 (LWP 10801)  0x00cc7422 in __kernel_vsyscall ()
  18 Thread 0x8c03ab70 (LWP 10802)  0x00cc7422 in __kernel_vsyscall ()
  17 Thread 0x8bfe9b70 (LWP 10805)  0x00cc7422 in __kernel_vsyscall ()
  16 Thread 0x8bf68b70 (LWP 10806)  0x00cc7422 in __kernel_vsyscall ()
  15 Thread 0x8bee7b70 (LWP 10808)  0x00cc7422 in __kernel_vsyscall ()
  14 Thread 0x8be96b70 (LWP 10810)  0x00cc7422 in __kernel_vsyscall ()
  13 Thread 0x8bcffb70 (LWP 10813)  0x00cc7422 in __kernel_vsyscall ()
  12 Thread 0x8bbfab70 (LWP 10814)  0x00cc7422 in __kernel_vsyscall ()
  11 Thread 0x8bb58b70 (LWP 10819)  0xb48c6e7a in ?? ()
  10 Thread 0x8b9ffb70 (LWP 10821)  0x00cc7422 in __kernel_vsyscall ()
  9 Thread 0x8b9aeb70 (LWP 10822)  0x00cc7422 in __kernel_vsyscall ()
  8 Thread 0x8b95db70 (LWP 10823)  0x00cc7422 in __kernel_vsyscall ()
  7 Thread 0x8b90cb70 (LWP 10824)  0x00cc7422 in __kernel_vsyscall ()
  6 Thread 0x8b8bbb70 (LWP 10825)  0x00cc7422 in __kernel_vsyscall ()
  5 Thread 0x8b55db70 (LWP 10833)  0x00cc7422 in __kernel_vsyscall ()
  4 Thread 0x8b777b70 (LWP 10836)  0x00cc7422 in __kernel_vsyscall ()
  3 Thread 0x8b5aeb70 (LWP 10837)  0x00cc7422 in __kernel_vsyscall ()
  2 Thread 0x8b0ffb70 (LWP 10871)  0x00cc7422 in __kernel_vsyscall ()
* 1 Thread 0xb77b06c0 (LWP 10788)  0x00cc7422 in __kernel_vsyscall ()
(gdb) thread 11
[Switching to thread 11 (Thread 0x8bb58b70 (LWP 10819))]#0  0xb48c6e7a in ?? ()
(gdb) bt
#0  0xb48c6e7a in ?? ()
#1  0x75d9dde9 in ?? ()
#2  0xc7717a73 in ?? ()
#3  0x0c102444 in ?? ()
#4  0xdd000000 in ?? ()
#5  0x8908245c in ?? ()
#6  0x45dbf475 in ?? ()
#7  0x241cddf4 in ?? ()
#8  0xff9597e8 in ?? ()
#9  0x9025ebff in ?? ()
Cannot access memory at address 0xdbdadd5f

The address of the thread (0xb48c6e7a) looks wrong compared to all other
threads but I'm not sure what to make of it.

-- 
Applets use 100% of CPU
https://bugs.launchpad.net/bugs/551328
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.

Status in “openjdk-6” package in Ubuntu: New

Bug description:
Using several applets I'm finding the Lucid i386 applet plugin with Firefox 3.6 is using 100% CPU from the time the applet starts. Even if the applet is stopped by closing the parent window the java process continues using 100% of the CPU.

Examples of a sites where this can be experienced:

http://www.java.com/en/download/help/testvm.xml
http://kent.w3.org/People/mimasa/test/object/java/clock
http://www.spunkyworld.com/demos/chat/index.htm