Community
Participate
Working Groups
When previewing a report or running the report in embedded web browser, Eclipse Reporting 3.7.1 crashes with only the following messages: No bp log location saved, using default. [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is Gtk2. [000:000] Using Gtk2 toolkit [000:000] Warning(optionsfile.cc:22): Load: Could not open file [000:000] No bp log location saved, using default. [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is Gtk2. [000:000] Using Gtk2 toolkit [000:273] Warning(optionsfile.cc:22): Load: Could not open file [000:273] No bp log location saved, using default. [000:273] Browser XEmbed support present: 1 [000:273] Browser toolkit is Gtk2. [000:273] Using Gtk2 toolkit Opened debug file '/home/ceefour/tmp/mozdebug' It happens with all reports, even with a blank one. 1. Launch Eclipse for Java & Report Developers 3.7.1 64-bit in Ubuntu 11.04 64-bit 2. Create a new report 3. On the blank report, click Preview tab ...... crash Workaround: ./eclipse -vmargs -Dorg.eclipse.swt.browser.DefaultType=mozilla This solves the crashing problem entirely. Workaround found from: https://bugs.eclipse.org/bugs/show_bug.cgi?id=349837#c14 The (upstream) Eclipse bug was marked fixed as of 3.7.1 however it still requires the manual command-line argument to avoid the crash in Eclipse Reporting/BIRT 3.7.1. My sistem info: Linux annafi 2.6.38-12-generic #51+kamal3~mjgbacklight5-Ubuntu SMP Wed Oct 5 20:13:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux java version "1.6.0_26" Java™ SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot™ 64-Bit Server VM (build 20.1-b02, mixed mode) Source topic: http://www.birt-exchange.org/org/forum/index.php/topic/22743-birt-designer-crashes-when-prevewingrunning-in-embedded-web-browser
Blogged this at: http://eclipsedriven.blogspot.com/2011/10/how-to-fix-eclipse-birt-designer-371.html Hopefully it is helpful for other BIRT report developers having the same problem.
This has been reported a few other times, but getting a simple snippet to help understand the problem has eluded us so far (see bug 334466, bug 352819). The problem with this workaround is that on newer Ubuntu Systems (11.10), XULRunner has been removed, so you can't switch back to mozilla :-(.
Dup with 334466 *** This bug has been marked as a duplicate of bug 334466 ***
