| Summary: | konqueror crashes while requesting info about a friend in facebook | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Pol <xtekhne> |
| Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | groszdanielpub, kon_chr2000-linux, lacsilva, milamby, moose, mtadeunet, ph.fondrillon |
| Priority: | HI | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Result of first valgrind run
Result of second valgrind run |
||
|
Description
Pol
2010-01-23 19:38:02 UTC
*** Bug 227104 has been marked as a duplicate of this bug. *** *** Bug 221844 has been marked as a duplicate of this bug. *** *** Bug 234917 has been marked as a duplicate of this bug. *** *** Bug 237729 has been marked as a duplicate of this bug. *** *** Bug 230501 has been marked as a duplicate of this bug. *** *** Bug 222680 has been marked as a duplicate of this bug. *** *** Bug 208926 has been marked as a duplicate of this bug. *** *** Bug 237825 has been marked as a duplicate of this bug. *** *** Bug 230614 has been marked as a duplicate of this bug. *** OK, it's pretty clear we have an issue here, but I can't seem to get it to trigger myself, and running through facebook in valgrind comes up clean. Any ideas on how to get this crash to trigger semi-consistently would be helpful. Hi. I can reproduce this bug and probably provide you with the information you need. How should I run konqueror through valgrind (what parameters?) and where should I send the resulting output results? First, it would likely help the most if you could tell me how to reproduce it reliably.... since there is garbage collection involved even valgrind might not be able to help by itself.. But anyway, valgrind --num-callers=50 konqueror http://whatever &>log, and then attach it here. Created attachment 43860 [details]
Result of first valgrind run
Created attachment 43861 [details]
Result of second valgrind run
Ok! After hours of facebook I finally managed to reproduce the bug. The behavior is very erratic so I couldn't find a reliable way to reproduce it unless spending lots of time in facebook and crossing fingers. I'm posting two different valgrind logs which I hope might help. The first one was produced by: valgrind --num-callers=50 konqueror http://facebook.com 2&> konqueror.log Following the suggestions from the end of the first log I rerun a second time like so: valgrind --num-callers=50 --track-origins=yes --leak-check=full -v konqueror http://facebook.com 2&> konqueror2.log I did a lot of opening and closing tabs. If you need me to run more targeted tests, I'll be happy to do so. Just tell me how. Thanks. The first log is clean, but the second one reveals a bug. I doubt that that bug is what's underlying this report (I suspect it shows up only because of the slowdown caused by valgrind), but I won't know for sure until I've figured out why it occurs... Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |