Bug 459436 - Krita Nightly (c16388c) crashes when saving any file
Summary: Krita Nightly (c16388c) crashes when saving any file
Status: RESOLVED DUPLICATE of bug 459252
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: git master (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-20 10:34 UTC by Hologram
Modified: 2022-09-20 10:46 UTC (History)
1 user (show)

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


Attachments
log file (961 bytes, text/plain)
2022-09-20 10:34 UTC, Hologram
Details
This is the crash log. (28.86 KB, text/plain)
2022-09-20 10:34 UTC, Hologram
Details
Systeminfo (7.03 KB, text/plain)
2022-09-20 10:35 UTC, Hologram
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hologram 2022-09-20 10:34:11 UTC
Created attachment 152253 [details]
log file

SUMMARY
***
For some reason the latest nightly crashes when I save a file.
***

**Steps to reproduce**
Initially, I thought it might have to do with the file layers, but it even crashes on save when I start with this a plain template and initiate a save thereafter.



STEPS TO REPRODUCE
1. Create a new file
2. Hit save (Ctrl+S)

OBSERVED RESULT
After an initial pause of a few seconds, Krita closes. The document is not saved to disc, though it does appear under recent files in the taskbar. Clicking on the file prompts a message that the file is not available. 

SOFTWARE/OS VERSIONS
Windows: 10 version 19044
Qt Version: 5.12

ADDITIONAL INFORMATION
See attached log files.
And notice that I have plenty of disc space >160 GB on all discs.
Comment 1 Hologram 2022-09-20 10:34:42 UTC
Created attachment 152254 [details]
This is the crash log.
Comment 2 Hologram 2022-09-20 10:35:27 UTC
Created attachment 152255 [details]
Systeminfo
Comment 3 Halla Rempt 2022-09-20 10:46:13 UTC
This fixed a couple of commits later.

*** This bug has been marked as a duplicate of bug 459252 ***