BIRT Designer crashes when prevewing/running in embedded web browser

When previewing a report or running the report in embedded web browser, Eclipse Reporting 3.7 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'



My environment : Ubuntu 11.04 64-bit



Linux annafi 2.6.38-10-generic #44+kamal~mjgbacklight4-Ubuntu SMP Mon Jun 6 19:40:12 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux



java version "1.6.0_25"

Java(TM) SE Runtime Environment (build 1.6.0_25-b06)

Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)



Should I file a bug report, and where?

Comments

  • mwilliamsmwilliams BIRT Guru
    edited December 1969
    Does this happen with all reports? I have previewed reports with 3.7 and not seen this issue. That being said, I am not using Ubuntu or Linux. I am using Windows 7. Let me know.

    Regards,

    Michael Williams

    eSignLive Evangelism & Community Manager | eSignLive by VASCO
     
    Find me on:
    Twitter
    Facebook
    Blog

    LinkedIn

    eSignLive Developer Community
     
    Email me:
    Google: mwilliams.silanis@gmail.com

  • edited December 1969


    Does this happen with all reports? I have previewed reports with 3.7 and not seen this issue. That being said, I am not using Ubuntu or Linux. I am using Windows 7. Let me know.




    It happens with all reports, even with a blank one.



    • Launch Eclipse for Java & Report Developers 3.7 64-bit in Ubuntu 11.04 64-bit
    • Create a new report
    • On the blank report, click Preview tab ...... crash
  • mwilliamsmwilliams BIRT Guru
    edited December 1969
    Can you try re-installing to see if you got a bad download somehow?

    Regards,

    Michael Williams

    eSignLive Evangelism & Community Manager | eSignLive by VASCO
     
    Find me on:
    Twitter
    Facebook
    Blog

    LinkedIn

    eSignLive Developer Community
     
    Email me:
    Google: mwilliams.silanis@gmail.com

  • edited December 1969


    Can you try re-installing to see if you got a bad download somehow?




    I think it's this problem:



    Important: If you are running on recent released Linux distributions or 64-bit distributions you might be bumping into an Eclipse 3.7 regression bug that prevents the visual page editor to load and result in a hard crash of the visual VM. To avoid this problem you can run eclipse with a property to disable the visual page editor.







    eclipse -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false







    Alternatively you can try using



    http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/swt.xulrunner.patch



    as updatesite to install temporary SWT patch that works similar to the planned Eclipse 3.7.1 patch.




    Source: http://planet.jboss.org/post/chasing_a_white_rabbit_with_jboss_tools_3_3_m2



    Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=349837



    Unfortunately I've tried the patch update site on Eclipse Reporting 3.7 (with BIRT Designer) and it still crashes.
  • mwilliamsmwilliams BIRT Guru
    edited December 1969
    Have you tried the avoiding the visual page editor way? Does it still crash then? If neither way works for you, please log another bug for this.

    Regards,

    Michael Williams

    eSignLive Evangelism & Community Manager | eSignLive by VASCO
     
    Find me on:
    Twitter
    Facebook
    Blog

    LinkedIn

    eSignLive Developer Community
     
    Email me:
    Google: mwilliams.silanis@gmail.com

  • edited December 1969


    Have you tried the avoiding the visual page editor way? Does it still crash then? If neither way works for you, please log another bug for this.




    I'm using Indigo SR1 (Eclipse BIRT Reporting 3.7.1) and it still crashes.



    Launching Eclipse with:



    eclipse -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false



    has no effect, it still crashes.
  • edited December 1969
    I also tried running with: (inspired by https://bugs.eclipse.org/bugs/show_bug.cgi?id=340998 )



    ./eclipse -vmargs  -Dorg.eclipse.swt.browser.UseWebKitGTK=true



    but it still crashes.



    Here's the output when crashing:



    ceefour@annafi:/opt/eclipse_reporting$ ./eclipse
    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:001] Warning(optionsfile.cc:23): Load: Could not open file, err=2
    [000:001] No bp log location saved, using default.
    [000:001] Browser XEmbed support present: 1
    [000:001] Browser toolkit is Gtk2.
    [000:001] Using Gtk2 toolkit
    [000:011] Warning(optionsfile.cc:23): Load: Could not open file, err=2
    [000:011] No bp log location saved, using default.
    [000:011] Browser XEmbed support present: 1
    [000:011] Browser toolkit is Gtk2.
    [000:011] Using Gtk2 toolkit
    Opened debug file '/home/ceefour/tmp/mozdebug'



    Here are list of log files, let me know if you need anything from here: (note: ReportEngine_*.log files are all empty)



    ceefour@annafi:/opt/eclipse_reporting$ find /home/ceefour/spaces/reporting/ -iname '*2011_10_30*.log'
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.chart.engine/org.eclipse.birt.chart.engine_2011_10_30_10_00_46_659.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.enablement.oda_2011_10_30_10_23_05.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/ReportEngine_2011_10_30_10_26_03.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.enablement.oda_2011_10_30_10_27_00.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.enablement.oda_2011_10_30_10_26_03.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.connectivity.oda_2011_10_30_10_29_01.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.connectivity.oda_2011_10_30_10_24_28.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.enablement.oda_2011_10_30_10_29_01.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.enablement.oda_2011_10_30_10_25_01.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/ReportEngine_2011_10_30_10_23_42.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.connectivity.oda_2011_10_30_10_23_42.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.connectivity.oda_2011_10_30_10_27_00.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.enablement.oda_2011_10_30_10_23_42.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.connectivity.oda_2011_10_30_10_23_05.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.enablement.oda_2011_10_30_10_24_28.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/ReportEngine_2011_10_30_10_27_00.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/ReportEngine_2011_10_30_10_29_01.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/ReportEngine_2011_10_30_10_25_01.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/ReportEngine_2011_10_30_10_23_05.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.connectivity.oda_2011_10_30_10_26_03.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/org.eclipse.datatools.connectivity.oda_2011_10_30_10_25_01.log
    /home/ceefour/spaces/reporting/.metadata/.plugins/org.eclipse.birt.report.viewer/logs/ReportEngine_2011_10_30_10_24_28.log
  • edited October 2011
    I found a 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 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(TM) SE Runtime Environment (build 1.6.0_26-b03)

    Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)



    I'll file a separate bug report for Eclipse BIRT project.
  • edited October 2011
  • mwilliamsmwilliams BIRT Guru
    edited December 1969
    Thanks for all the updates on the workaround and bug report! Let us know whenever you have questions! :)

    Regards,

    Michael Williams

    eSignLive Evangelism & Community Manager | eSignLive by VASCO
     
    Find me on:
    Twitter
    Facebook
    Blog

    LinkedIn

    eSignLive Developer Community
     
    Email me:
    Google: mwilliams.silanis@gmail.com

Sign In or Register to comment.