Bug 389151 - Crash when opening or creating document
Summary: Crash when opening or creating document
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.3.3
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-01-18 11:16 UTC by ollie.pearn
Modified: 2018-10-29 02:04 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash file (166.32 KB, text/plain)
2018-01-18 11:22 UTC, ollie.pearn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ollie.pearn 2018-01-18 11:16:16 UTC
I have just upgraded to 3.3.3, portable edition, but installed to a local hard drive.  Krita opens ok, but crashes when opening or creating a new document. The system is Windows 7 32 bit, and it is possible that the portable apps has installed the 64 bit version - I haven't found anything on their forums through.  I've looked for the kritacrash file - but isn't present - perhaps because it is the portable application.  I've also tried changing the display options to ANGLE from Auto and disabling the acceleration as recommended in the documentation with no change in the programs behaviour.
Comment 1 ollie.pearn 2018-01-18 11:22:54 UTC
Created attachment 109963 [details]
crash file

Found crash file
Comment 2 Halla Rempt 2018-01-18 11:38:44 UTC
Hi Ollie,

If you'd try to run a 64 bit application on a 32 bit system, then it wouldn't even start, so that's not probable. I haven't any 32 bits systems left to test with, and my Windows 7 system is broken, too...

The crash file is pretty weird: it seems to crash in opengl-related code when loading the icon for a tool, but that is very unlikely to be the case, especially if disabling canvas acceleration doesn't make a difference.

Could you retry after resetting Krita's configuration? See https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration
Comment 3 ollie.pearn 2018-01-19 08:33:46 UTC
Hi Boudewijn,
I've tried renaming the file and have the same problem again.  Doesn't seem to make any difference.  I've tried to put on the Portable Apps forum too - but their account setup has a Google Captcha and I'm in China:(
Comment 4 ollie.pearn 2018-01-20 01:07:56 UTC
Downgraded to 3.3.2 and runs with no problems
Comment 5 Halla Rempt 2018-01-24 09:36:34 UTC
With "portable", do you mean a version you downloaded from someplace other than krita.org? And could you test with the latest beta?
Comment 6 ollie.pearn 2018-01-26 11:38:28 UTC
It's installed from here https://portableapps.com/ -  runs without needing to install to the computer.  They are packaged as .paf files. I could have a shot at running the beta version through the creator - which version do you recommend?
Comment 7 Halla Rempt 2018-01-26 17:19:14 UTC
We definitely don't support any repackaged version of Krita. We already supply Krita in a zip archive that you can unpack anywhere. That also makes it possible to install debug symbols to debug the crash: https://docs.krita.org/Dr._Mingw_debugger

Oh, and I was wool-gathering when I recommended using the beta: that is not available for 32 bits systems at this point, I had forgotten about that.
Comment 8 Alvin Wong 2018-01-26 17:44:34 UTC
@Boud
The backtraces appear to point to some sort of heap corruption (would be my guess). Some of the crashes appears to be triggered when loading cursors, some appears to be related to QtSvg, but neither are necessarily related to the actual bug. The backtraces themselves could also be misleading so don't trust them fully...

I can't think of any specific reasons, but I can perhaps try a 32-bit Windows 7 VM tomorrow to see if things work...
Comment 9 Andrew Crouthamel 2018-09-28 03:40:38 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 10 Andrew Crouthamel 2018-10-29 02:04:50 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!