Summary: | Konqueror crashes when navigating back or forward in history | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Rune Jensen <jensrune> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, gfh, h.ozinga, kojot350, mail, maksim, nadavkav, porten, simon |
Priority: | NOR | ||
Version: | 4.1.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Backtrace |
Description
Rune Jensen
2008-10-12 22:44:46 UTC
No, www.itavisen.no does it. Not www.vg.no I get a crash, too. But the backtrace is different so it might be about a different bug. Steps: 1.) http://www.itavisen.no/ 2.) Click on any of the "Lesernes beste nettips" below the KUDOS logo 3.) I ended up on http://www.kudos.no/needCookies.html (not sure whether this is a bug by its own or my setting) 4.) Click on the brower Back button quickly after each other Will add backtrace. Created attachment 27838 [details]
Backtrace
I can't reproduce this bug on openSuSE 11, KDE 4.1.2 Navigating back or forward where www.itavisen.no is the target will cause the crash Looking at the source, I think maybe it should be two & in this if sentence, it should be a logical AND and not the bit AND operator ? void Collector::markStackObjectsConservatively(void *start, void *end) .......... if ((blocks[block] == blockAddr) & (offset <= lastCellOffset)) { if (((CollectorCell *)x)->u.freeCell.zeroIfFree != 0) { JSCell *imp = reinterpret_cast<JSCell *>(x); if (!imp->marked()) imp->mark(); ......... see also bug #167966 and bug #170185 and bug #173066 They are all dealing with crashes on back/next-navigation. this bug is still there in release KDE 4.1.3 "release 4.9" same problem with www.imdb.com Bug 179573 may be a duplicate of this *** Bug 179573 has been marked as a duplicate of this bug. *** *** Bug 179813 has been marked as a duplicate of this bug. *** *** Bug 182231 has been marked as a duplicate of this bug. *** any plans on this one? *** This bug has been marked as a duplicate of bug 170185 *** |