Bug 709967
| Summary: | [abrt] midori-0.3.6-1.fc15: WebCore::PluginView::start: Process /usr/bin/midori was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joachim Frieben <jfrieben> | ||||||||||
| Component: | icedtea-web | Assignee: | Deepak Bhole <dbhole> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 15 | CC: | dbhole, kevin, maxamillion, omajid | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:43644d2f1f6651a3595bb97cd74c68c3f4b9bb1e | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-06-09 16:04:48 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Joachim Frieben
2011-06-02 06:12:27 UTC
Created attachment 502428 [details]
File: maps
Created attachment 502429 [details]
File: backtrace
- chromium-11.0.696.71-1.fc15: executes version applet as expected - epiphany-3.0.3-1.fc15: no result but no crash either - firefox-4.0.1-2.fc15: executes version applet as expected If you do: echo 1 > /proc/sys/vm/overcommit_memory does it operate as you expect? No, midori crashes simply as before. When run from the shell, then the following output is associated with the crash: ** (midori:3482): DEBUG: NP_Initialize succeeded *** NSPlugin Wrapper *** WARNING:(../src/npw-wrapper.c:3499):invoke_NP_Initialize: assertion failed: (rpc_method_invoke_possible(g_rpc_connection)) java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.1) (fedora-57.1.10.1.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) *** NSPlugin Viewer *** ERROR: rpc_end_sync called when not in sync! Segmentation fault (core dumped) Interesting. If you do: yum remove icedtea-web and re-run does everything work as expected? (In reply to comment #6) No, as one would expect, the absence of the Java plugin simply causes the version applet not to be executed. Accordingly, there is no crash either. Sorry, yeah. Lets see if the icedtea folks can see anything with this... Can you please start firefox from the terminal as: ICEDTEAPLUGIN_DEBUG=true firefox 2>&1 | tee console.log and then post the resulting console.log file? Created attachment 503715 [details] Java debug log for http://javatester.org/version.html The command suggested in comment 9 did not work: the output file was empty. However, 'ICEDTEAPLUGIN_DEBUG=true firefox' did the job well. (In reply to comment #10) > Created attachment 503715 [details] > Java debug log for http://javatester.org/version.html > > The command suggested in comment 9 did not work: the output file was empty. > However, 'ICEDTEAPLUGIN_DEBUG=true firefox' did the job well. It doesn't look like the browser crashed there -- did it? Created attachment 503803 [details] Java debug log for http://javatester.org/version.html (In reply to comment #11) This bug report is about midori, right? Doh! Sorry, force of habit using 'firefox' :) I will take a look into it tomorrow. My apologies for not making the connection earlier. This is the same issue as Bug# 691259. I am going to mark this a duplicate of that bug. It is fixed upstream: http://icedtea.classpath.org/hg/release/icedtea-web-1.0/rev/4169f6296ed7 I will be doing an icedtea-web 1.0.3 release on Monday (June 13th) and will build it for F15 soon after that. *** This bug has been marked as a duplicate of bug 691259 *** |