Bugzilla – Full Text Bug Listing
| Summary: | Segmentation fault while using MPC with embedded browser | ||
|---|---|---|---|
| Product: | [Technology] MPC | Reporter: | Peter Severin <peter> |
| Component: | Install | Assignee: | Project Inbox <mpc.install-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | grant_gayed, m.hariri |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Peter Severin
MPC just uses the browser support provided by the Platform/SWT. Seems to be a known issue but cannot be resolved at Eclipse. If you have more input, I think it would be good to post your thoughts on bug 334466. Marking this as duplicate. *** This bug has been marked as a duplicate of bug 334466 *** Peter can you attach the dump file that's created when the segfault happens? It's likely a different issue than the bug that this report is marked as a duplicate of. Grant, I think there is no dump file. I just get "Segmentation fault" message and no "core dumped". If you can tell me where to look I'll get it for you. Sun/Oracle JRE creates file "hs_*", and IBM JRE creates file "javacore.*". In both cases '*' represents a long string of numbers. I think these are written to the java launch directory, so if you're running eclipse at the command line then this would be the directory containing the eclipse executable. Segfaults usually (though not always) result in these dump files being written. Grant, I had to play with ulimit to obtain the core dump. It's a file named core. The same that you get for native apps. It's 40M compressed. If you think it can help you I'll send you a link for download. That sounds like a binary dump of everything. I think there should be an accompanying text file (hs_* or javacore.*) in the same directory that's much smaller and can be attached here. There is nothing else in the current directory... I am making these tests with a fresh version of Eclipse Indigo and Sun's Java 1.6.0_26. Happening here too, actually I first saw this segmentation fault when clicking "preview" on any BIRT report, and then I came by this ticket and checked the steps and it happened for me too. The log when previewing a BIRT report: ** (Eclipse:2028): DEBUG: NP_Initialize ** (Eclipse:2028): DEBUG: NP_Initialize succeeded 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 ** (Eclipse:2028): DEBUG: NP_Initialize ** (Eclipse:2028): DEBUG: NP_Initialize succeeded ** (Eclipse:2028): DEBUG: NP_Initialize ** (Eclipse:2028): DEBUG: NP_Initialize succeeded [000:030] Warning(optionsfile.cc:23): Load: Could not open file, err=2 [000:031] No bp log location saved, using default. [000:031] Browser XEmbed support present: 1 [000:031] Browser toolkit is Gtk2. [000:031] Using Gtk2 toolkit ** (Eclipse:2028): DEBUG: NP_Initialize ** (Eclipse:2028): DEBUG: NP_Initialize succeeded Segmentation fault |