Summary: | Konqueror crashed in operator new | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Christopher Yeleighton <giecrilj> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | adawit |
Priority: | NOR | ||
Version: | 4.7.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christopher Yeleighton
2012-01-16 20:55:33 UTC
The specified test URL is not accessable. I get access forbidden error page from the server. Can you reliably reproduce this crash ? Or is this one of those crashes that happen one time and cannot be reproduced ? (In reply to comment #1) > The specified test URL is not accessable. I get access forbidden error page > from the server. That is right, and Konqueror crashed on that (of all things). > Can you reliably reproduce this crash ? No. (In reply to comment #2) > (In reply to comment #1) > > The specified test URL is not accessable. I get access forbidden error page > > from the server. > > That is right, and Konqueror crashed on that (of all things). Well, cannot reproduce it here. Tried visiting the link multiple times in both rendering engines (khtml/webkit). No crash. And the back trace is also weird. The crash seems to have occurred on unrelated thread (not the main event thread) inside of a system call. > > Can you reliably reproduce this crash ? > > No. And that makes it impossible to identify the problem. Will leave ticket open for a while to see if you encounter this crash again and perhaps provide a way to reproduce it. (In reply to comment #3) > The crash seems to have occurred on unrelated thread (not the main event > thread) inside of a system call. The crash seems to have been elicited by a memory exception inside operator new. (In reply to comment #4) > (In reply to comment #3) > > > The crash seems to have occurred on unrelated thread (not the main event > > thread) inside of a system call. > > The crash seems to have been elicited by a memory exception inside operator > new. Right, inside QThreadPrivate::createEventDispatcher. However, that does not tell us much. We cannot infer that the crash is in QThread at all because we cannot see if something like a nested event loop is involved somewhere in that thread. Cannot reproduce this crash. Feel free to reopen this if the issue occurs again with newer version of KDE (4.8.0 or higher). |