Bug 133172

Summary: random konqueror crash in libqt-mt
Product: [Fedora] Fedora Reporter: Ellen Shull <ellenshull>
Component: qtAssignee: Than Ngo <than>
Status: CLOSED WORKSFORME QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-10-15 16:49:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
KDE crash handler backtrace none

Description Ellen Shull 2004-09-22 02:03:54 UTC 
Description of problem:
I had Konqueror open behind some other windows with several tabs open:
slashdot, tvguide, anandtech, technologyreview, not sure what else.  I
was actually writing an email in KMail when the KDE crash handler came
up with a crash in Konqueror.  The most recent identifiable call in
the chain is in qt, so you you get the bug report until you can pass
the buck to someone else ;-)

Version-Release number of selected component (if applicable):
qt-3.3.3-5
kdebase-3.3.0-3
kdelibs-3.3.0-2 <-- I notice there's a newer kdelibs in rawhide right
now which is to 'fix a bug in ksslopen #114835'; I will update to it,
but what are the chances it's the problem?

How reproducible:
This is the first time I've seen this crash.  I have no idea what
triggered it, but given the QTimer::timeout in the call chain, I don't
think it's something I manually triggered.

Additional info:
Will attach the backtrace from the KDE crash handler.
Comment 1 Ellen Shull 2004-09-22 02:04:54 UTC 
Created attachment 104103 [details]
KDE crash handler backtrace
Comment 2 Than Ngo 2004-09-22 09:07:18 UTC 
i don't think the fix in ksslopen can trigger this problem. Sorry i
cannot reproduce it. Can you provide more exact instructions on how to
reproduce it? thanks
Comment 3 Than Ngo 2004-10-15 16:49:19 UTC 
please reopen it again if you have exactly instructions how to
reproduce this problem. Thanks