Krita crash on new canvas and on load image. Tested kra and jpeg. The version prior to this build crashed too in the same way.
I tried to remove krita.rc and my added plugins but it still crashed.
1 Like
Same here. Tried add “Full disk access” in assumption this is some security clashing - did not helped…
Does it seem to be similar to this topic?
Seems no… App windows appear normally, but nothing can be loaded after that. Crash happens even when i click on “New - Create”. No brush use possible (compared to your link)
In console i see the following
(base) IRs-iMac:Backend ipv6$ cd /Applications/krita520.app/Contents/MacOS
(base) IRs-iMac:MacOS ipv6$ ls
krita krita_version kritarunner
(base) IRs-iMac:MacOS ipv6$ cd /Applications/krita520.app/Contents/MacOS; ./krita
qt.qpa.fonts: Populating font family aliases took 107 ms. Replace uses of missing font family ".AppleSystemUIFont" with one that exists to avoid this cost.
Invalid profile : "/Library/ColorSync/Profiles//WebSafeColors.icc"
krita.lib.pigment: Replacing color space factory "LABA" "L*a*b* (16-bit integer/channel, unmanaged)" with "LABA" "L*a*b*/Alpha (16-bit integer/channel)"
krita.lib.pigment: Replacing color space factory "RGBA" "RGB (8-bit integer/channel, unmanaged)" with "RGBA" "RGB/Alpha (8-bit integer/channel)"
krita.lib.pigment: Replacing color space factory "RGBA16" "RGB (16-bit integer/channel, unmanaged)" with "RGBA16" "RGB/Alpha (16-bit integer/channel)"
QObject::startTimer: Timers cannot have negative intervals
/Applications/krita520.app/Contents/Frameworks/krita-python-libs/krita added to PYTHONPATH
libpng warning: iCCP: known incorrect sRGB profile
ASSERT (krita): "producer->is_valid()" in file /Users/Packaging/KritaBuild/krita/libs/ui/KisPlaybackEngineMLT.cpp, line 300
Abort trap: 6
(base) IRs-iMac:MacOS ipv6$
The assert shows it’s caused by the animation audio rewrite. I’m not getting this on Windows or Linux, only macOS.
I get the feeling that the crash happen when creating the canvas object. I’ve tried to read the crash information that supposed to be sent to Apple. I don’t understand if it is to be read up to down or reverse. This is what I see in the first rows:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x1835a4724 __pthread_kill + 8
1 libsystem_pthread.dylib 0x1835dbc28 pthread_kill + 288
2 libsystem_c.dylib 0x1834e9ae8 abort + 180
3 QtCore 0x1095965c8 0x10957c000 + 107976
4 QtCore 0x109858eb4 QMessageLogger::fatal(char const*, …) const + 120
5 libkritaglobal.19.dylib 0x1077058c8 0x107700000 + 22728
6 libkritaui.19.dylib 0x106d5a36c KisPlaybackEngineMLT::setupProducer(boost::optional) + 1180
7 libkritaui.19.dylib 0x106d5aa0c KisPlaybackEngineMLT::setCanvas(KoCanvasBase*) + 1040
8 libkritaflake.19.dylib 0x1062e5a2c 0x106298000 + 317996
9 libkritaui.19.dylib 0x106d0f82c KisViewManager::setCurrentView(KisView*) + 6
It’s caused when trying to load MLT for audio playback, which is currently triggered when loading the canvas even if it doesn’t contain animation or audio.
The cause appears to be that libmltkrita.so isn’t being packaged in the DMG file for some reason. Without it Krita cannot connect to MLT.
The top is the most recent, so if you want to read it chronologically that would be in reverse. setCurrentView calls setCanvas, which calls setupProducer, which hits an assert (QMessageLogger::fatal).
3 Likes
I’ve asked @IvanYossi to take a look.
1 Like
This has been fixed in the latest Nightly (aa2d167).
3 Likes
Can confirm now it is working for me, no crash. Tnx!
1 Like
No crash here. 
1 Like