Bug 349781 - Loop in object tree (KoParagraphStyle->KoStyleManager->KoParagraphStyle->...)
Summary: Loop in object tree (KoParagraphStyle->KoStyleManager->KoParagraphStyle->...)
Status: CONFIRMED
Alias: None
Product: calligracommon
Classification: Applications
Component: text-tool (other bugs)
Version First Reported In: unspecified
Platform: Other All
: NOR minor
Target Milestone: ---
Assignee: Calligra Words Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-01 13:32 UTC by Jonathan Ringstad
Modified: 2021-03-09 08:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Ringstad 2015-07-01 13:32:46 UTC
There appears to be a loop in the object tree somewhere.

Relevant log from IRC:

<Smjert> Amadiro_: well KoStyleManager line 159 is where it sets d->defaultParagraphStyle as parent which is initialized at line 113, and to its constructor "this" is passed, so that KoStyleManager is the parent and the loop is created
<Smjert> also line 164 there's the second setParent to the same thing
<Smjert> and given that very near to those two setParent there's an instantation of other KoParagraphStyle, is natural to wonder if it shouldn't have been style->setParent

This crashes current versions of the GammaRay Qt debugger, see the following bugreport on the GammaRay tracker: https://github.com/KDAB/GammaRay/issues/138#issuecomment-117516264

It might be worth to untangle this loop (as it's probably a bug anyway?) in order to make krita work with current and older version of the GammaRay debugger (and possibly other tools that could be useful in aiding debugging.)

Reproducible: Always
Comment 1 Halla Rempt 2015-08-25 12:33:02 UTC
Yes, it's a bug, but it needs to be reported against the calligra libraries.
Comment 2 Justin Zobel 2021-03-09 01:22:29 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.