2.3.12 displays seemingly random seg faults on MacOS, making the software unusable. Unfortunately, despite a lot of trying I cannot make the crash deterministic.
After loading the software, it is likely to hard crash soon - usually within a few minutes of use. The point of crash is always upon clicking a control or refocussing the window i.e. it does not crash when otherwise not being interacted with. In fact simply opening the software, opening a recipe, going to work with other things in macOS (like typing a crash report!) and then focusing back on the Beersmith window can trigger a crash. I think a recipe has to be open to trigger the crash but this is hard to verify for certain. Upon restarting BeerSmith, if changes were made to a recipe they have not been saved.
Interestingly, saving does still work. One has to load the recipe, make the change, and then force quit. The change is saved and persists though invocations. However if a crash happens then edits are usually lost. I have given BeerSmith "full disk access" in macOS security.
Pertinent details from the crash log:
Model: MacBookPro14,2, BootROM 429.50.1.0.0, 2 processors, Dual-Core Intel Core i5, 3.1 GHz, 16 GB, SMC 2.44f5
Graphics: kHW_IntelIrisGraphics650Item, Intel Iris Plus Graphics 650, spdisplays_builtin
After loading the software, it is likely to hard crash soon - usually within a few minutes of use. The point of crash is always upon clicking a control or refocussing the window i.e. it does not crash when otherwise not being interacted with. In fact simply opening the software, opening a recipe, going to work with other things in macOS (like typing a crash report!) and then focusing back on the Beersmith window can trigger a crash. I think a recipe has to be open to trigger the crash but this is hard to verify for certain. Upon restarting BeerSmith, if changes were made to a recipe they have not been saved.
Interestingly, saving does still work. One has to load the recipe, make the change, and then force quit. The change is saved and persists though invocations. However if a crash happens then edits are usually lost. I have given BeerSmith "full disk access" in macOS security.
Pertinent details from the crash log:
Code:
Process: BeerSmith2 [96120]
Identifier: BeerSmith-LLC.BeerSmith2
Version: 2.3.12 (2312)
Code Type: X86-64 (Native)
Parent Process: ??? [1] [POSTER NOTE: this is three ?s but the forum software is rendering it with an emoticon...]
OS Version: macOS 11.0.1 (20B29)
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000118651000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_platform.dylib 0x00007fff2037c0a9 _platform_memmove$VARIANT$Haswell + 41
1 com.apple.SkyLight 0x00007fff24bb79d2 __CGPixelAccessDataInitialize + 683
2 com.apple.SkyLight 0x00007fff24c6b194 __CGPixelAccessAccessBitmapData + 524
3 com.apple.SkyLight 0x00007fff24c6ba4c SLPixelAccessCreateImageFromRect + 570
4 com.apple.AppKit 0x00007fff230d3026 -[NSBitmapImageRep initWithFocusedViewRect:] + 1636
5 BeerSmith-LLC.BeerSmith2 0x00000001072eea37 0x10719b000 + 1391159
6 BeerSmith-LLC.BeerSmith2 0x00000001073fd77d 0x10719b000 + 2500477
7 BeerSmith-LLC.BeerSmith2 0x00000001073fb6d4 0x10719b000 + 2492116
8 BeerSmith-LLC.BeerSmith2 0x00000001073fb2b7 0x10719b000 + 2491063
9 BeerSmith-LLC.BeerSmith2 0x0000000107725c2a 0x10719b000 + 5811242
10 BeerSmith-LLC.BeerSmith2 0x000000010776eb2f 0x10719b000 + 6109999
11 BeerSmith-LLC.BeerSmith2 0x000000010752656b 0x10719b000 + 3716459
12 BeerSmith-LLC.BeerSmith2 0x00000001071a0612 0x10719b000 + 22034
13 BeerSmith-LLC.BeerSmith2 0x0000000107526617 0x10719b000 + 3716631
14 BeerSmith-LLC.BeerSmith2 0x000000010763ecd7 0x10719b000 + 4865239
15 BeerSmith-LLC.BeerSmith2 0x000000010763eab3 0x10719b000 + 4864691
16 BeerSmith-LLC.BeerSmith2 0x00000001076406e6 0x10719b000 + 4871910
17 BeerSmith-LLC.BeerSmith2 0x00000001076417bd 0x10719b000 + 4876221
18 BeerSmith-LLC.BeerSmith2 0x00000001076404df 0x10719b000 + 4871391
19 BeerSmith-LLC.BeerSmith2 0x0000000107640450 0x10719b000 + 4871248
20 BeerSmith-LLC.BeerSmith2 0x000000010764090d 0x10719b000 + 4872461
21 BeerSmith-LLC.BeerSmith2 0x00000001074ce1a5 0x10719b000 + 3355045
22 BeerSmith-LLC.BeerSmith2 0x0000000107302ef6 0x10719b000 + 1474294
23 BeerSmith-LLC.BeerSmith2 0x00000001073c08e4 0x10719b000 + 2250980
24 BeerSmith-LLC.BeerSmith2 0x00000001073be68e 0x10719b000 + 2242190
25 com.apple.AppKit 0x00007fff22dba5fc _NSViewDrawRect + 139
26 com.apple.AppKit 0x00007fff234e1709 -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 2115
27 com.apple.AppKit 0x00007fff234e1a9a -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 3028
... many more stack traces, and traces of other threads. But it is always thread 0 which hits the seg fault.
Model: MacBookPro14,2, BootROM 429.50.1.0.0, 2 processors, Dual-Core Intel Core i5, 3.1 GHz, 16 GB, SMC 2.44f5
Graphics: kHW_IntelIrisGraphics650Item, Intel Iris Plus Graphics 650, spdisplays_builtin