Project

General

Profile

Bug #11619

macOS crash on B&W photo

Added by Alex Popov over 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
General
Target version:
-
Start date:
05/18/2017
Due date:
% Done:

0%

Affected Version:
2.2.4
System:
Mac OS X
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Please let me know how I can make this issue better.

I used VueScan to scan some 35mm B&W negatives at 6400ppi in 16-bit greyscale as JPEGs. When I tried to open them, darktable crashed.
It continued to crash at lunch until I deleted the cache and config folders.

I used ImageMagick to resize the files (thinking perhaps 56MP files are too big) by 50% down to ~13MP. The same behaviour happened again.

Is this a known issue or am I doing something wrong? I'd love to be able to help resolve this any way I can.

Thank you

Machine:
2012 15" Retina MacBook Pro
16GB RAM
256GB SSD
2.3 Ghz quad-core i7 processor
Intel HD 4000 and Nvidia GT 650M graphics cards

macOS 10.12.5

darkroom_crash.log Magnifier - Crashlog (101 KB) Alex Popov, 05/20/2017 01:47 AM

bw-roll2-0013.jpg - Example photo that crashes. (3.18 MB) Alex Popov, 05/20/2017 01:47 AM

History

#1 Updated by Roman Lebedev over 1 year ago

That "bt" looks as if the problem is in gtk/cairo

#2 Updated by Alex Popov over 1 year ago

Is there anything I can do to try and clarify the issue?

I used homebrew to install the latest gtk+ and cairo; the crash persists (after launching normally with cleared .config and .cache folders)

#3 Updated by Roman Lebedev over 1 year ago

Alex Popov wrote:

Is there anything I can do to try and clarify the issue?

No clue, i have never used that system.

I used homebrew to install the latest gtk+ and cairo; the crash persists (after launching normally with cleared .config and .cache folders)

That will most definitively not help. gtk is likely bundled into the dmg, and the system version is irrelevant.

#4 Updated by Guido Flohr about 1 year ago

I can reproduce the crash with darktable built from git master on OS X Sierra. My crash log looks different though:

abort() called
  • error for object 0x7fa726893200: incorrect checksum for freed object - object was probably modified after being freed.

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fffcb51cd42 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffcb60a457 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffcb482420 abort + 129
3 libsystem_malloc.dylib 0x00007fffcb57cf5d szone_error + 626
4 libsystem_malloc.dylib 0x00007fffcb57e925 small_free_list_remove_ptr_no_clear + 766
5 libsystem_malloc.dylib 0x00007fffcb57ecb2 free_small + 881
6 libjpeg.9.dylib 0x0000000101dd6130 free_pool + 218
7 libjpeg.9.dylib 0x0000000101db57d6 jpeg_abort + 29
8 libjpeg.9.dylib 0x0000000101db81fa jpeg_finish_decompress + 158
9 libdarktable.dylib 0x0000000100078388 dt_imageio_jpeg_read + 456 (imageio_jpeg.c:700)
10 libdarktable.dylib 0x0000000100078b0f dt_imageio_open_jpeg + 303 (imageio_jpeg.c:741)
11 libdarktable.dylib 0x0000000100075dd1 dt_imageio_open_ldr + 225 (imageio.c:497)
12 libdarktable.dylib 0x0000000100076f88 dt_imageio_open + 88 (imageio.c:941)
13 libdarktable.dylib 0x000000010008b2f2 dt_mipmap_cache_get_with_caller + 1346 (mipmap_cache.c:763)
14 libimport.so 0x000000011c86cfb6 _lib_import_single_image_callback + 1142 (import.c:858)
etc.

I have converted the same jpeg with darktable-cli to a png. That works sometimes. Sometimes it crashes.

Converting the jpeg with djpeg does not crash, even 100 times in a loop while using the computer.

Running djpeg through valgrind does not show anything interesting. Running darktable through valgrind does not work here, sorry.

Also available in: Atom PDF