Bug 423204 - Crash in KoShape::parent
Summary: Crash in KoShape::parent
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 4.2.8
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-19 04:54 UTC by Jeremy Rose
Modified: 2020-06-19 10:27 UTC (History)
1 user (show)

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

Attachments
Full crash report (100.51 KB, text/plain)
2020-06-19 04:54 UTC, Jeremy Rose 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Rose 2020-06-19 04:54:34 UTC 
Created attachment 129509 [details]
Full crash report

SUMMARY
Null dereference in KoShape::parent

STEPS TO REPRODUCE
I don't have reliable repro steps, but this happened when I toggled a layer to be invisible.

OBSERVED RESULT

Crash with SIGSEGV at address 0x0000000000000090

Truncated stack trace (full report attached):
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libkritaflake.18.dylib        	0x000000011166b598 KoShape::parent() const + 8
1   libkritaui.18.dylib           	0x000000010fc3dbae KisNodeShape::editabilityChanged() + 478
2   org.qt-project.QtCore         	0x0000000113383112 QObject::event(QEvent*) + 770
3   org.qt-project.QtWidgets      	0x000000011217c110 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272
4   org.qt-project.QtWidgets      	0x000000011217d4c5 QApplication::notify(QObject*, QEvent*) + 581
5   libkritaui.18.dylib           	0x000000010ff18ada KisApplication::notify(QObject*, QEvent*) + 26


SOFTWARE/OS VERSIONS
macOS: 10.14.6
Comment 1 Halla Rempt 2020-06-19 10:27:53 UTC 
Hi Jeremy,

I'm afraid we cannot do much with this report because we've just released 4.3.0 which has this part of the code refactored. Could you please update to the latest release (https://krita.org/en/item/krita-4-3-0-released/)? If the same crash happens again, please do reopen the bug report.