Bug 448496
| Summary: | Gecko engine hangs | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christoph Höger <choeger> |
| Component: | gnash | Assignee: | Patrice Dumas <pertusus> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | gecko-bugs-nobody, mcepl, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-10-19 18:15:09 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: | |||
|
Description
Christoph Höger
2008-05-27 09:42:00 UTC
How long the firefox stays frozen? Isn't it just another reproduction of bad bug 439908 (which is upstream https://bugzilla.mozilla.org/show_bug.cgi?id=421482)? There seems to be recovery after any time. Also, FF seems not to hang, but wait
for some input on socket.
read(3, 0x97886b4, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=11, events=POLLIN|POLLPRI}, {fd=12,
events=POLLIN|POLLPRI}, {fd=13, events=POLLIN|POLLPRI}, {fd=17, events=POLLIN},
{fd=10, events=POLLIN|POLLPRI}, {fd=46, events=POLLIN}, {fd=61, events=POLLIN},
{fd=18, events=POLLIN}], 11, 0) = 0
select(62, [61], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1211910140, 806580}, NULL) = 0
read(3, 0x97886b4, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
fd 3 is a unix socket, so it seems that ff waits for some answer from a plugin.
That could propably be gnash. But anyway I would call it a firefox bug because
rendering should not stop because of some defect plugin.
(In reply to comment #2) > fd 3 is a unix socket, so it seems that ff waits for some answer from a plugin. > That could propably be gnash. But anyway I would call it a firefox bug because > rendering should not stop because of some defect plugin. Could I get result of rpm -qa \*firefox\* \*mozilla\* \*nspluginwrapper\* \*flashsupport\* please? Thank you Of course: firefox-3.0-0.60.beta5.fc9.i386 nspluginwrapper-0.9.91.5-27.fc9.i386 mozilla-filesystem-1.9-2.fc9.i386 firefox-3.0-0.65.cvs20080416.fc10.i386 here (rawhide). It reliably hangs when accesing trac pages, when going to comment on LWN, when asking this bugzilla something, ... Also happens at random. The hangs are unrecoverable (once I went out and came back an hour or so, still hung). Sometimes it shows some disk activity, but it mostly goes away soon. I /do/ love FF, but I'm forced to use galeon now. firefox-3.0-0.65.cvs20080416.fc10.i386 mozilla-filesystem-1.9-2.fc10.i386 flash-plugin-9.0.124.0-release.i386 (from Adobe; gnash just shows a white space on YouTube) Hmm, weird -- I certainly cannot reproduce this neither with trac, nor LWN, nor this bugzilla ;-). Could I ask for a favor, please? Could you download the last Firefox upstream binary from http://www.mozilla.com/en-US/firefox/all-beta.html and try, whether you can reproduce it? Thank you very much. I could reproduce it with ff3, but after removing gnash it was gone forever - so guess who's fault its been! Oh, thanks. Reassigning to the true criminal ;-). What is your gnash version? When I reported that bug it has been the lates stable gnash verion in the repositories. Thats what I found in my logs: May 20 14:44:16 Installed: gnash-0.8.2-2.fc9.i386 May 20 23:10:24 Installed: gnash-plugin-0.8.2-2.fc9.i386 Jun 18 12:28:41 Erased: gnash Jun 18 12:28:43 Erased: gnash-plugin Hope that helps. Could you please try with the builds found at: http://koji.fedoraproject.org/koji/buildinfo?buildID=55493 I am going to to give it a try, when all new signed updates are through. 0.8.3 should be in the updates now. Just tested it over the weekend, seems to be fixed in combination with ff 3.0.2 |