Community
Participate
Working Groups
Build Identifier: 20110218-0911 Report Preview does not work. Crashes eclipse. With Fedora packaged java: JRE version: 6.0_20-b20 # Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) # Derivative: IcedTea6 1.9.6 # Distribution: Fedora release 15 (Rawhide), package fedora-53.1.9.6.fc15-i386 # Problematic frame: # C [libxul.so+0xda5f18] With Java installed from Sun: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x4b9996c3, pid=5367, tid=3066755952 # # JRE version: 6.0_24-b07 # Java VM: Java HotSpot(TM) Server VM (19.1-b02 mixed mode linux-x86 ) # Problematic frame: # C [libxul.so+0xd796c3] # Reproducible: Always Steps to Reproduce: 1. Remove workspace and .eclipse directories for clean environment 2. Unpack eclipse-reporting-helios-SR2-linux-gtk.tar.gz in home directory 3. run ./eclipse --clean -vm /usr/bin/java 4. Create new reporting project 5. Create new blank report 6. Click on preview tab
Created attachment 191640 [details] Fedora Packaged Java
Created attachment 191641 [details] Sun Java
I have installed: 1) eclipse-reporting-helios-SR2-linux-gtk.tar.gz and 2 birt-report-designer-all-in-one-linux-gtk-2_6_2.tar.gz With the same results.
Filed a bug with icedtea.classpath.org and confirmed that this is a problem with the RC 2 version of xulrunner shipped with Fedora 15. If xulrunner 2.0 is uninstalled and replaced with previous xulrunner 1.9.2.10, this problem goes away. Not sure where this goes from here..... Fedora? Java? Eclipse? Mozilla? http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=678 http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=673
Switch to platform team for further investigation.
Might be related to Bug# 319123. Moving to Equinox
bug319123 should have been fixed in Helios SR2. Moving to launcher.
Should this bug be still opened?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.