Bug 392712 - Crash of krita at the moment of creating or opening a document
Summary: Crash of krita at the moment of creating or opening a document
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-04-04 12:44 UTC by JBJ
Modified: 2018-10-29 01:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Krita trace (29.97 KB, text/plain)
2018-04-04 12:44 UTC, JBJ
Details
trace #114 (30.09 KB, text/plain)
2018-04-05 11:44 UTC, JBJ
Details
screen capture (315.79 KB, image/png)
2018-04-05 11:45 UTC, JBJ
Details

Note You need to log in before you can comment on or make changes to this bug.
Description JBJ 2018-04-04 12:44:51 UTC
Created attachment 111816 [details]
Krita trace

I installed Krita 4.0 (downloaded on the official website) and at the first start I got a python error as described in the bug report 392227. 
So I installed the last nightly build version (Version 4.0.0.51 #113). Krita started properly but it crash systematically while opening any old document or images or crating new document. 
I attached the trace file.
Comment 1 Halla Rempt 2018-04-04 13:04:39 UTC
Hm, I tried that build just now on my SP3 with a clean config, and I didn't have a crash. Have you created or deleted any color palettes?
Comment 2 JBJ 2018-04-04 13:11:40 UTC
(In reply to Boudewijn Rempt from comment #1)
> Hm, I tried that build just now on my SP3 with a clean config, and I didn't
> have a crash. Have you created or deleted any color palettes?

It was fresh install and I didn't touch anything related to the color palettes.
Comment 3 Halla Rempt 2018-04-04 13:20:03 UTC
Had you had an earlier install of Krita on that system?
Comment 4 Halla Rempt 2018-04-04 13:34:01 UTC
Git commit a42c7e9137e2d8993a08eef6228ac26ec203f231 by Boudewijn Rempt.
Committed on 04/04/2018 at 13:33.
Pushed by rempt into branch 'master'.

Check whether the colorset is valid before using it

M  +2    -2    libs/widgets/KoColorPopupAction.cpp
M  +2    -1    libs/widgets/KoColorSetWidget.cpp
M  +2    -2    libs/widgets/KoColorSetWidget.h

https://commits.kde.org/krita/a42c7e9137e2d8993a08eef6228ac26ec203f231
Comment 5 Halla Rempt 2018-04-04 13:34:59 UTC
Okay, I've added an extra check for validity at the point where the crash seems to occur, but I still cannot reproduce the crash. Could you check with tomorrow's nightly build whether this fixes the issue for you (or exposes a different crash...)
Comment 6 JBJ 2018-04-04 13:37:54 UTC
(In reply to Boudewijn Rempt from comment #3)
> Had you had an earlier install of Krita on that system?

I did have a previous version of krita. The last official release of the v3. It was performing well. I did uninstall it before installing the v4
Comment 7 JBJ 2018-04-04 13:38:58 UTC
(In reply to Boudewijn Rempt from comment #5)
> Okay, I've added an extra check for validity at the point where the crash
> seems to occur, but I still cannot reproduce the crash. Could you check with
> tomorrow's nightly build whether this fixes the issue for you (or exposes a
> different crash...)

I am going to try the nightly build of tomorrow
thanks!
Comment 8 JBJ 2018-04-05 11:44:33 UTC
Created attachment 111842 [details]
trace #114
Comment 9 JBJ 2018-04-05 11:45:20 UTC
Created attachment 111843 [details]
screen capture
Comment 10 JBJ 2018-04-05 11:47:32 UTC
I tried the nightly build #114 but krita is still crashing when I try to create or open a document. I attach the corresponding trace.
Comment 11 Halla Rempt 2018-04-06 08:56:52 UTC
Can you try with a clean configuration? It's clear you've got my changes in that build because the backtrace now happens in the Qt shared pointer code, but I'm very puzzled because I just cannot reproduce :-(
Comment 12 JBJ 2018-04-06 10:26:09 UTC
I did a fresh install and it is now working!
I have to mention something that I forgot to indicate. I have 2 partition on my hard drive  (C and D) and for work purpose all the User files and folder are on D. Before I was trying to install Krita on C in default path (C:\Program Files\...), and I had this crash at the moment of creating or opening document.
Now I did a clean install in a folder on D and it work perfectly!
The point is I don't know if it's working because it is on D or because of the clean install. I hope it can give you some indication of what could have happen. Anyway, thank you very much for your help!

PS:  I use the nightly build #114
Comment 13 Halla Rempt 2018-04-09 08:59:23 UTC
Git commit 5abfca0340164a66abbdebb8dce7507407ba108f by Boudewijn Rempt.
Committed on 09/04/2018 at 08:57.
Pushed by rempt into branch 'krita/4.0'.

Check whether the colorset is valid before using it
(cherry picked from commit a42c7e9137e2d8993a08eef6228ac26ec203f231)

M  +2    -2    libs/widgets/KoColorPopupAction.cpp
M  +2    -1    libs/widgets/KoColorSetWidget.cpp
M  +2    -2    libs/widgets/KoColorSetWidget.h

https://commits.kde.org/krita/5abfca0340164a66abbdebb8dce7507407ba108f
Comment 14 Andrew Crouthamel 2018-09-28 03:32:36 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 15 Andrew Crouthamel 2018-10-29 01:59: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!