| Summary: | crash (SEGV) in khtml TreeShared<DOM::NodeImpl> | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Matthew Woehlke <mwoehlke.floss> |
| Component: | khtml | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | jakob.bugs, maksim, Regnaron, StormByte |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Matthew Woehlke
2008-07-08 17:05:21 UTC
...silly karma :-), unconfirming until someone else can reproduce I can't reproduce using Konqueror from trunk (kdelibs rev. 829304). Note : the bt is the same as the one in bug 164348. *** This bug has been marked as a duplicate of 127147 *** This one may be slightly different, actually, since it doesn't have to do with backwards navigation. They just share a crash point... as above.. still reproducible in r829547 after clean builds of libs and base (which seems to have fixed the nsplugin problem also). Note: I don't get the crash *every* time, but it feels like it dies more often than not. I can reproduce with a clean session, i.e. launch konq (don't restore session if asked), paste the address and hit 'enter' to load the site, usually but not always -> SEGV. I'm on Fedora 8 on an x64 (KDE4 built from sources as in the report headers) http://www.sagemath.org (from bug 164384) doesn't crash for me *** Bug 168819 has been marked as a duplicate of this bug. *** Not really reproducible, but I managed to crash konqueror on this page at least once. (I clicked on the title (to go to the page itself) and then hit the back button which made konqueror-4.1.0 crash for me). At least for me, the page from bug #168954 crashes with the same backtrace, but far more reliably. *** Bug 168954 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of 164384 *** Err, wrong number. *** This bug has been marked as a duplicate of 164348 *** |