Bug 130494 - KHTMLPart dtor crashes when its KHTMLView is dtor'd first
Summary: KHTMLPart dtor crashes when its KHTMLView is dtor'd first
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: investigated, needs_verification, triaged
Depends on:
Blocks:
 
Reported: 2006-07-09 03:10 UTC by Ilya Konstantinov
Modified: 2018-10-21 04:55 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya Konstantinov 2006-07-09 03:10:58 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Fedora RPMs

When a KHTMLView is destroyed, e.g. as part of the destruction of a widget hierarchy, the subsequent destruction of the KHTMLPart which uses this view will crash. This is due to line such as:

  disconnect( partManager(), ...

This line relies on partManager() not to be null, but partManager() may be null when d->m_view is null (and d->m_view is a QGuardedPtr, so it'll be null as soon as the KHTMLView is dtor'd, for whatever reason).

By the way, this is a real bug which caused Amarok 1.4.1 to crash on exit. The workaround was to manually delete the KHTMLParts before the widget hierarchy is destroyed.
Comment 1 Frank Osterfeld 2006-08-23 09:38:19 UTC
Do you have a backtrace and/or a test case?
I also had the problem with crashes on exit when not manually deleting the parts first. But IIRC it hadn't to do with partManager(), but with the html cache.
Comment 2 Ilya Konstantinov 2006-08-23 09:50:46 UTC
I don't have a test case; however, this was the fix I've provided for Amarok bug 130495 and it indeed worked to solve the crash.
Comment 3 Eduardo Robles Elvira 2008-06-06 01:27:53 UTC
Is it still happening to you in any recent version of KDE? We won't fix KDE 3.5 anymore, so please test with KDE 4.0.5 or KDE 4.1 when it's out.
Comment 4 FiNeX 2008-11-22 02:22:07 UTC
Hi: is this bug still valid with the new KDE4?
Comment 5 FiNeX 2009-08-23 18:18:41 UTC
Marked as needsinfo.

@Ilya: please, could you answer to the latest questions? Moreover a backtrace could be useful. Thanks
Comment 6 Nicolas L. 2010-08-19 10:35:32 UTC
do you still reproduce this bug ? if yes can you provide the needed backtrace ?


thank you a lot
Comment 7 Andrew Crouthamel 2018-09-20 21:56:34 UTC
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 set the bug status 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!
Comment 8 Andrew Crouthamel 2018-10-21 04:55:07 UTC
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!