Bug 389569

Summary:	Assertion failure when exiting
Product:	[Applications] krita	Reporter:	lou
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	halla
Priority:	NOR	Keywords:	triaged
Version First Reported In:	git master (please specify the git hash!)
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description lou 2018-01-28 19:50:33 UTC

I'm on a dev build and somehow hit this when closing krita:

> SAFE ASSERT (krita): "!sanityCheckPointer.isValid()" in file /tmp/nix-build-krita-4.0.0-pre2c.drv-0/krita-1b1695a/libs/ui/KisDocument.cpp, line 490

I have no idea how to reproduce it at the moment.

I had some modified documents open for which I told krita not to save changes, and I also tried unsuccessfully, to reproduce https://bugs.kde.org/389567 in that session. I don't remember anything else.

I think I only had to click through the confirm dialog once though, so that would mean I probably only had one document open....

Comment 1 Halla Rempt 2018-01-30 09:16:34 UTC

Did you run python scripts in that session?

Comment 2 lou 2018-02-01 13:10:15 UTC

I my python script setup is broken at the moment (env vars not set up correctly or something, I forgot.) so I shoudn't have been able to run any scripts.

Comment 3 Halla Rempt 2018-02-28 10:30:41 UTC

What are your build options? A safe_assert actually shouldn't cause a segfault. And could you update and try to reproduce again? We've done a lot of work this month :-)

Comment 4 Andrew Crouthamel 2018-09-28 03:13:51 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 5 Andrew Crouthamel 2018-10-29 02:11:22 UTC

Dear Bug Submitter,

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!