Bug 254623 – dev-java/swt-3.4-r2: Can't run SWT apps, window flash, 100% CPU

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Giuliano 2009-01-12 11:41:23 UTC]

Can't run any SWT app.



Reproducible: Always

Steps to Reproduce:
Via Java Web Start:
  javaws http://www.eclipse.org/swt/jws/controlexample.jnlp

Or yet:
  wget http://www.eclipse.org/swt/jws/controlexample.jar
  java -cp /usr/share/swt-3.4/lib/swt.jar:controlexample.jar org.eclipse.swt.examples.controlexample.ControlExample

This test using an SWT build not provided by Gentoo, doesn't succeed either:
  wget http://www.eclipse.org/swt/jws/controlexample.jar
  wget http://www.eclipse.org/swt/jws/swt-gtk-linux-x86.jar
  java -cp swt-gtk-linux-x86.jar:controlexample.jar org.eclipse.swt.examples.controlexample.ControlExample

Actual Results:  
"something" (a window) rapidly flashes on the screen, the CPU goes to 100% and nothing happens. No messages are shown on the terminal.

Expected Results:  
Normal application startup.

The output of strace ends with:

(strace -o out.txt java -cp /usr/share/swt-3.4/lib/swt.jar:controlexample.jar org.eclipse.swt.examples.controlexample.ControlExample)

munmap(0xb7f75000, 106842)              = 0
mmap2(NULL, 331776, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7dab000
mprotect(0xb7dab000, 4096, PROT_NONE)   = 0
clone(child_stack=0xb7dfb4b4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xb7dfbbd8, {entry_number:6, base_addr:0xb7dfbb90, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0xb7dfbbd8) = 8183
futex(0xb7dfbbd8, FUTEX_WAIT, 8183, NULL) = ? ERESTARTSYS (To be restarted)
--- SIGINT (Interrupt) @ 0 (0) ---
futex(0xb7dfbbd8, FUTEX_WAIT, 8183, NULL) = ? ERESTARTSYS (To be restarted)
--- SIGTERM (Terminated) @ 0 (0) ---
futex(0xb7dfbbd8, FUTEX_WAIT, 8183, NULL) = ? ERESTARTSYS (To be restarted)
+++ killed by SIGKILL +++

[Comment 1 Vlastimil Babka (Caster) (RETIRED) 2009-01-12 12:26:13 UTC]

Please post emerge --info and what jdk/jre are you using for the tests. Try other ones too, might be a bug of jdk, not swt.

[Comment 2 Giuliano 2009-01-12 13:14:00 UTC]

Created attachment 178163 [details]
output of emerge --info

[Comment 3 Giuliano 2009-01-12 13:23:58 UTC]

Same behaviour using JRE 1.6 and 1.5 ...

balrog swt # java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode)
balrog swt # java -cp /usr/share/swt-3.4/lib/swt.jar:controlexample.jar org.eclipse.swt.examples.controlexample.ControlExample
^C
balrog swt # eselect java-vm set system 1
balrog swt # java -version
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Server VM (build 1.5.0_16-b02, mixed mode)
balrog swt # java -cp /usr/share/swt-3.4/lib/swt.jar:controlexample.jar org.eclipse.swt.examples.controlexample.ControlExample
^C

[Comment 4 Patrice Clement (RETIRED) 2015-04-04 19:54:32 UTC]

Hi there. This bug is quite old. Do you still experience it? Please comment or I will close this issue. Thank you.

[Comment 5 Patrice Clement (RETIRED) 2015-04-08 12:08:07 UTC]

Apparently not. Closing it.