Invalid profile : "/Library/ColorSync/Profiles//WebSafeColors.icc" "Web Safe Colors"
Floating point exception: 8

So, that explains it. It's weird, though, since I did fix a similar bug on Windows, and invalid profiles should be disregarded now. I'll have to check whether we do something weird on macOS. Could you mail me that icc file? You can send it to boud@valdyas.org.

Edit: no, that's not it... I've got the same profile on my mac, and Krita does disregard it. The floating point exception must come from somewhere else.

Do you have the developer tools installed on your mac?

I get the same profile error but I have never seen a crash of the like. Only with the dev tools installed we could get to the source of failure.

I admittedly have very little tech background, like Mac osX developer tools?
Edit: I'm downloading Homebrew via the Terminal, hopefully this is a step in the right direction.

All you need is to install the command line tools

Here some post I found on google about it http://osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x/

After that you need touse the terminal to open krita. In the terminal (Assuming krita is in Application folder)

Code: Select all

lldb /Applications/krita.app/Contents/MacOS/krita


Press Enter, what until the line starts with (lldb), then launch krita

Code: Select all

run

after it crashes the terminal will allow you to type again. type

Code: Select all

bt all

Copy all the contents of the terminal and paste it somewhere like pastebin (or here?) for us to see. If there is a crash it will tell us where, also if there are other problems.

https://pastebin.com/8s14QkuQ
There ya are

thank you! Now the error is much more clear.

was there any other output before backtrace thread #1? the faulty resource should be listed there.

(lldb) run
Process 3552 launched: '/Applications/krita.app/Contents/MacOS/krita' (x86_64)
2019-06-21 08:38:28.649187-0500 krita[3552:279282] Set style "fusion"
2019-06-21 08:38:32.606577-0500 krita[3552:279282] Invalid profile : "/Library/ColorSync/Profiles//WebSafeColors.icc" "Web Safe Colors"
Process 3552 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC (code=EXC_I386_DIV, subcode=0x0)
frame #0: 0x0000000102feb745 libkritapigment.18.dylib`KoColorSet::Private::loadKplGroup(QDomDocument const&, QDomElement const&, KisSwatchGroup*) + 2357
libkritapigment.18.dylib`KoColorSet::Private::loadKplGroup:
-> 0x102feb745 <+2357>: idivl %ecx
0x102feb747 <+2359>: movl %eax, %ebx
0x102feb749 <+2361>: movq -0x80(%rbp), %rdi
0x102feb74d <+2365>: movl (%rdi), %eax
Target 0: (krita) stopped.
(lldb) bt all
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC (code=EXC_I386_DIV, subcode=0x0)

Ah, now we're getting somewhere! Do you have in ~/Library/Application Support/krita/palettes any custom palettes that end with the .kpl extension? If so, check whether moving them out of the way makes a difference? If that does make a difference, could you make a zip of them and share them with us?

I do not, all the palettes are .gpl

But you do have local .gpl palettes? Maybe those are the culprit then... I'd like to take a look at them in that case.

Deleting the .gpl files didn't appear to do anything unfortunately.

And the crash log is still giving an error in the same place?

Appears so?

Process 7627 launched: '/Applications/krita.app/Contents/MacOS/krita' (x86_64)
2019-06-24 06:43:13.998125-0500 krita[7627:970916] Set style "fusion"
2019-06-24 06:43:15.942558-0500 krita[7627:970916] Invalid profile : "/Library/ColorSync/Profiles//WebSafeColors.icc" "Web Safe Colors"
Process 7627 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC (code=EXC_I386_DIV, subcode=0x0)
frame #0: 0x0000000102feb745 libkritapigment.18.dylib`KoColorSet::Private::loadKplGroup(QDomDocument const&, QDomElement const&, KisSwatchGroup*) + 2357
libkritapigment.18.dylib`KoColorSet::Private::loadKplGroup:
-> 0x102feb745 <+2357>: idivl %ecx
0x102feb747 <+2359>: movl %eax, %ebx
0x102feb749 <+2361>: movq -0x80(%rbp), %rdi
0x102feb74d <+2365>: movl (%rdi), %eax
Target 0: (krita) stopped.
(lldb) bt all
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC (code=EXC_I386_DIV, subcode=0x0)
* frame #0: 0x0000000102feb745 libkritapigment.18.dylib`KoColorSet::Private::loadKplGroup(QDomDocument const&, QDomElement const&, KisSwatchGroup*) + 2357
frame #1: 0x0000000102fe35cf libkritapigment.18.dylib`KoColorSet::Private::loadKpl() + 2447
frame #2: 0x0000000102fd882d libkritapigment.18.dylib`KoColorSet::Private::init() + 1085
frame #3: 0x0000000102fd83e7 libkritapigment.18.dylib`KoColorSet::loadFromDevice(QIODevice*) + 119
frame #4: 0x0000000102fd814b libkritapigment.18.dylib`KoColorSet::load() + 139
frame #5: 0x0000000102a114d7 libkritawidgets.18.dylib`___lldb_unnamed_symbol406$$libkritawidgets.18.dylib + 1383
frame #6: 0x0000000102a05286 libkritawidgets.18.dylib`KoResourceServerProvider::KoResourceServerProvider() + 1558
frame #7: 0x0000000102a06ca3 libkritawidgets.18.dylib`KoResourceServerProvider::instance() + 99
frame #8: 0x00000001013c60bc libkritaui.18.dylib`KisApplication::loadResources() + 124
frame #9: 0x00000001013c7253 libkritaui.18.dylib`KisApplication::start(KisApplicationArguments const&) + 1411
frame #10: 0x000000010000f8c0 krita`main + 9296
frame #11: 0x00007fffa15c5235 libdyld.dylib`start + 1
frame #12: 0x00007fffa15c5235 libdyld.dylib`start + 1
thread #2
frame #0: 0x00007fffa16f444e libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fffa17de621 libsystem_pthread.dylib`_pthread_wqthread + 1426
frame #2: 0x00007fffa17de07d libsystem_pthread.dylib`start_wqthread + 13
thread #3
frame #0: 0x00007fffa16f444e libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fffa17de48e libsystem_pthread.dylib`_pthread_wqthread + 1023
frame #2: 0x00007fffa17de07d libsystem_pthread.dylib`start_wqthread + 13
thread #4
frame #0: 0x00007fffa16f444e libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fffa17de621 libsystem_pthread.dylib`_pthread_wqthread + 1426
frame #2: 0x00007fffa17de07d libsystem_pthread.dylib`start_wqthread + 13
thread #6
frame #0: 0x00007fffa16f444e libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fffa17de621 libsystem_pthread.dylib`_pthread_wqthread + 1426
frame #2: 0x00007fffa17de07d libsystem_pthread.dylib`start_wqthread + 13
thread #7
frame #0: 0x00007fffa16f444e libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fffa17de48e libsystem_pthread.dylib`_pthread_wqthread + 1023
frame #2: 0x00007fffa17de07d libsystem_pthread.dylib`start_wqthread + 13
thread #8
frame #0: 0x00007fffa16f444e libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fffa17de621 libsystem_pthread.dylib`_pthread_wqthread + 1426
frame #2: 0x00007fffa17de07d libsystem_pthread.dylib`start_wqthread + 13
thread #9, name = 'com.apple.CFSocket.private'
frame #0: 0x00007fffa16f3eb6 libsystem_kernel.dylib`__select + 10
frame #1: 0x00007fff8bdfdc3a CoreFoundation`__CFSocketManager + 682
frame #2: 0x00007fffa17de93b libsystem_pthread.dylib`_pthread_body + 180
frame #3: 0x00007fffa17de887 libsystem_pthread.dylib`_pthread_start + 286
frame #4: 0x00007fffa17de08d libsystem_pthread.dylib`thread_start + 13
thread #10, name = 'com.apple.NSEventThread'
frame #0: 0x00007fffa16ec34a libsystem_kernel.dylib`mach_msg_trap + 10
frame #1: 0x00007fffa16eb797 libsystem_kernel.dylib`mach_msg + 55
frame #2: 0x00007fff8bdc29d4 CoreFoundation`__CFRunLoopServiceMachPort + 212
frame #3: 0x00007fff8bdc1e61 CoreFoundation`__CFRunLoopRun + 1361
frame #4: 0x00007fff8bdc16b4 CoreFoundation`CFRunLoopRunSpecific + 420
frame #5: 0x00007fff89a03f02 AppKit`_NSEventThread + 205
frame #6: 0x00007fffa17de93b libsystem_pthread.dylib`_pthread_body + 180
frame #7: 0x00007fffa17de887 libsystem_pthread.dylib`_pthread_start + 286
frame #8: 0x00007fffa17de08d libsystem_pthread.dylib`thread_start + 13

Looks pretty similar to me.

Yes... That's the same location. And it's a place where did fix a divide by zero error recently, but that code is only executed if there's a broken kpl file that Krita tries to load! And that bug was fixed, so the current nightly builds (https://binary-factory.kde.org/job/Krit ... cOS_Build/) and 4.2.2 which will be released this week won't have that issue.

if you start Krita like this:

QT_LOGGING_RULES="krita.*=true" /Applications/krita.app/Contents/MacOS/krita then we might have even more data to look into.

Edit: the signed 4.2.2 dmg is now also available for testing from https://download.kde.org/stable/krita/4.2.2/ -- we'll officially release it on thursday.