| Summary: | Epiphany crash while executing java script code | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Herbert Poetzl <herbert> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | cjw, dmorganec, fundawang, jani.valimaa, mageia, marja11, reinout |
| Version: | 1 | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | epiphany-2.30.6-2.mga1.src.rpm, webkit-1.2.7-4.mga1.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
Crash on Recovery
Second Recovery Run Third Recovery Run Fourth Recovery Run Fifth Recovery Run Trace from the "lady gaga" search Trace from the first "lady gaga" search recovery |
||
|
Description
Herbert Poetzl
2011-05-11 14:43:57 CEST
Created attachment 381 [details]
Crash on Recovery
Created attachment 382 [details]
Second Recovery Run
Created attachment 383 [details]
Third Recovery Run
Created attachment 384 [details]
Fourth Recovery Run
Created attachment 385 [details]
Fifth Recovery Run
Hi Herbert, is this still an issue? If yes, do you have an URL that consistently results in a crash that we can test with? (In reply to comment #6) > Hi Herbert, is this still an issue? yes, still an issue, it crashes at least 5 times a day, sometimes several times in a row on recovery ... > If yes, do you have an URL that consistently results in a crash that we can test with? I don't think there is such thing, it seems to me like a race condition, but I can easily test and/or debug this if you tell me how/what to do because if I start browsing/opening pages it usually takes less than a minute to trigger and often takes several 'recoveries' to get it up and running again ... I just did a test and it worked like a charm: - start clean epiphany - open www.google.com - search for "lady gaga" - middle mouse open the first 10-15 links - close some of the tabs while they are loading - do another search on google that was the session, epiphany exited with the 'usual' segfault ... Created attachment 733 [details]
Trace from the "lady gaga" search
Created attachment 734 [details]
Trace from the first "lady gaga" search recovery
Just to confirm, still an issue ... i.e. epiphany crashing after a few pages/tabs, recovery usually takes 3-10 attempts because epiphany crashes on the recovery as well ... Can you reproduce with a new user (xguest for example) ? Version:
Cauldron =>
1 (In reply to comment #11) > Can you reproduce with a new user (xguest for example) ? Yes, switched to xguest, took about 30 seconds to crash Epiphany and cause BugBuddy to go crazy about it ... Couldn't capture a debug trace as gdb doesn't work in the rbash environment Seems nobody can reproduce this 'bug' Whiteboard:
(none) =>
unconfirmed Sounds to me like nobody is trying, because I can trigger it on at least 3 different systems here, one has been 'upgraded' from Mandriva, 2 are new installs from scratch (default install with gnome selected), and all of them show the described crash within a few seconds of loading and clicking. I'm willing to do some debugging but last time I checked msot involved 'debug' packages didn't even contain debug symbols ... Indeed I can comfirm that it crash. I will check tomorrow for installing debug, but I don't know much think about that. As there is no maintainer of epiphany (for now), I add the three most commiter of the package. CC:
(none) =>
cjw, dmorganec, fundawang from glancing at the traces, it looks to me like webkit (webkit-1.2.7-4.mga1, webkit1.0-1.2.7-4.mga1, libwebkitgtk1.0_2-1.2.7-4.mga1) might be to blame, in general, I presume that the java script code is either compiled incorrectly or overwritten/freed before executed which in turn leads to the crashes at dynamic addresses .. but that's just me guessing here ... (In reply to comment #16) > from glancing at the traces, it looks to me like webkit (webkit-1.2.7-4.mga1, > webkit1.0-1.2.7-4.mga1, libwebkitgtk1.0_2-1.2.7-4.mga1) might be to blame, I agree. The webkitgtk version in Mageia 1 is just really outdated (the most recent stable version is 1.6.1). I'm afraid there's no other option than to live with the situation until the next Mageia release that will contain the latest Epiphany and WebkitGTK unless someone backports Gnome 3.2 to Mageia 1. CC:
(none) =>
reinout (In reply to comment #17) > (In reply to comment #16) > > from glancing at the traces, it looks to me like webkit (webkit-1.2.7-4.mga1, > > webkit1.0-1.2.7-4.mga1, libwebkitgtk1.0_2-1.2.7-4.mga1) might be to blame, > > I agree. The webkitgtk version in Mageia 1 is just really outdated (the most > recent stable version is 1.6.1). I'm afraid there's no other option than to > live with the situation until the next Mageia release that will contain the > latest Epiphany and WebkitGTK unless someone backports Gnome 3.2 to Mageia 1. removing "unconfirmed" because it was confirmed by Manuel. Adding two cauldron committers of webkit to the cc of this bug, who weren't in it yet CC:
(none) =>
jani.valimaa, mageia, marja11 Sorry, Herbert /o\ maybe these things get fixed faster when you become a Mageia packager. I took your silence as a message that you don't want to become a Mageia packager anymore. Did I understand correctly? Well, the way things are developing now, there is hope there'll be a maintainer for webkit some day, look here for the statistics: http://kamil.mageia.org.pl/MageiaStats/ I would suggest you report this bug to https://bugs.webkit.org (In reply to comment #19) > Sorry, Herbert /o\ nothing to be sorry about on your part ... or did I miss something? > maybe these things get fixed faster when you become a Mageia packager. > I took your silence as a message that you don't want to become a Mageia > packager anymore. Did I understand correctly? well, I finally decided to step up as mageia maintainer (for some still unmaintained packages I'm using personally), but I don't think that I want to maintain webkit (no idea why such a central part doesn't have a maintainer yet, after all most drak* tools depend on webkit) > Well, the way things are developing now, there is hope there'll be a maintainer > for webkit some day, look here for the statistics: > http://kamil.mageia.org.pl/MageiaStats/ yeah, let's hope ... (In reply to comment #21) > (In reply to comment #19) > > Sorry, Herbert /o\ > nothing to be sorry about on your part ... or did I miss something? > No, I just dream of bug reports being triaged and assigned to the proper maintainer within a week after they're reported ;) > > well, I finally decided to step up as mageia maintainer (for some still > unmaintained packages I'm using personally), but I don't think that I want to > maintain webkit (no idea why such a central part doesn't have a maintainer yet, > after all most drak* tools depend on webkit) Great, welcome Herbert! Please add your name etc. here: https://wiki.mageia.org/en/Becoming_a_Mageia_Packager#Packaging_apprentice_candidates (In reply to comment #20) > I would suggest you report this bug to https://bugs.webkit.org Herbert, do you mind looking upstream to see whether there's already a bug report for this issue and if not, file one? Please give a link to the report once you're done. Thanks :) Keywords:
(none) =>
UPSTREAM (In reply to comment #22) > No, I just dream of bug reports being triaged and assigned to the proper > maintainer within a week after they're reported ;) sounds too good to be true :) > > well, I finally decided to step up as mageia maintainer (for some still > > unmaintained packages I'm using personally), but I don't think that I want to > > maintain webkit (no idea why such a central part doesn't have a maintainer yet, > > after all most drak* tools depend on webkit) > Great, welcome Herbert! > Please add your name etc. here: > https://wiki.mageia.org/en/Becoming_a_Mageia_Packager#Packaging_apprentice_candidates no need I guess, I've been already mentored and started to work as packager/maintainer. > (In reply to comment #20) > > I would suggest you report this bug to https://bugs.webkit.org > Herbert, do you mind looking upstream to see whether there's already a bug > report for this issue and if not, file one? Don't know if it was reported (yet) but I do not see those crashes on Cauldron (which uses a newer version of webkit), so I presume it is already fixed upstream ... so, either updating Mageia 1 or identifying and backporting the fix(es) from Cauldron would be the way to go here, but no chance without a maintainer ... > Please give a link to the report once you're done. Thanks :) will do some search when I find the time ... (In reply to comment #23) > > no need I guess, I've been already mentored and started to work as > packager/maintainer. > Totally missed that, but even better so :) I see, you already maintain 6 packages including util-vserver now :) (I think I mixed up some vserver packages in the past, if you see me mixing up names again, please correct me. I won't be offended, I even mix up the names of my children with those of my brothers, so I know I do such things) > > Don't know if it was reported (yet) but I do not see those crashes on Cauldron > (which uses a newer version of webkit), so I presume it is already fixed > upstream ... > > so, either updating Mageia 1 or identifying and backporting the fix(es) from > Cauldron would be the way to go here, but no chance without a maintainer ... > > > Please give a link to the report once you're done. Thanks :) > > will do some search when I find the time ... Thanks :) (In reply to comment #23) > Don't know if it was reported (yet) but I do not see those crashes on Cauldron > (which uses a newer version of webkit), so I presume it is already fixed > upstream ... > > so, either updating Mageia 1 or identifying and backporting the fix(es) from > Cauldron would be the way to go here, but no chance without a maintainer ... webkitgtk updated its libmjaor since 1.4.0 (which is latest stable version of 1.2.7), backporting it will require rebuilding all the packages depending it, which is not suggested. (In reply to comment #25) > (In reply to comment #23) > > Don't know if it was reported (yet) but I do not see those crashes on Cauldron > > (which uses a newer version of webkit), so I presume it is already fixed > > upstream ... > > > > so, either updating Mageia 1 or identifying and backporting the fix(es) from > > Cauldron would be the way to go here, but no chance without a maintainer ... > webkitgtk updated its libmjaor since 1.4.0 (which is latest stable version of > 1.2.7), backporting it will require rebuilding all the packages depending it, > which is not suggested. @ Funda In other words: "wontfix" ? (In reply to comment #26) > @ Funda > > In other words: "wontfix" ? Yes, it is difficult to fix, as there is no code branch upstream at svn.webkit.org (In reply to comment #27) > (In reply to comment #26) > > @ Funda > > > > In other words: "wontfix" ? > Yes, it is difficult to fix, as there is no code branch upstream at > svn.webkit.org OK, thx for replying, Funda Closing Status:
NEW =>
RESOLVED |