Author Topic: 2.3.12 unusable on MacOS due to seg faults  (Read 3459 times)

Offline iangray

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 6
2.3.12 unusable on MacOS due to seg faults
« on: January 10, 2021, 07:22:27 AM »
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:

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


Offline jomebrew

  • Global Moderator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 1045
    • Jomebrew
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #1 on: January 11, 2021, 09:51:01 AM »
What OSx version?

Offline iangray

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 6
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #2 on: January 11, 2021, 11:16:06 AM »
It's right there in the log:
OS Version:            macOS 11.0.1 (20B29)


Offline jomebrew

  • Global Moderator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 1045
    • Jomebrew
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #3 on: January 11, 2021, 11:52:42 AM »
I was going to offer some help but with your snarky reply, nah.

It's right there in the log:
OS Version:            macOS 11.0.1 (20B29)

Offline iangray

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 6
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #4 on: January 11, 2021, 01:19:17 PM »
I wasn't trying to be snarky, I was trying to show that I had done my due diligence in posting as complete a bug report as possible.

Please don't threaten to withhold help down to a simple misreading.

Offline iangray

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 6
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #5 on: January 12, 2021, 11:26:10 AM »
To update, the dev has confirmed to me that BeerSmith 2 isn't supported on macOS 11 and isn't going to work. There is at least now a warning note on the website.

Jomebrew, for someone who describes themselves as "rude, crude, offensive and of questionable character" you got pretty upset at me trying to gently rib you for not reading my post. Apologies, no offence meant.
« Last Edit: January 12, 2021, 11:28:05 AM by iangray »

Offline jomebrew

  • Global Moderator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 1045
    • Jomebrew
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #6 on: January 12, 2021, 03:11:34 PM »
To update, the dev has confirmed to me that BeerSmith 2 isn't supported on macOS 11 and isn't going to work. There is at least now a warning note on the website.

Jomebrew, for someone who describes themselves as "rude, crude, offensive and of questionable character" you got pretty upset at me trying to gently rib you for not reading my post. Apologies, no offence meant.

In the context of wanting to help someone, saying "it is RIGHT THERE in crash log data" is a little off putting. There wasn't a smiley face for me to say DOH! and smack my head even though I am not familiar with MacOS crash dumps. I did look at the bottom hoping it would be there. I did note you had a mid 2017 MacBook Pro and wasn't likely dealing with old hardware issue.

I had to search what 11.0.1 translated to as the release name which I have to do every time someone say OSx Version x.y.z..  Upon seeing it was Big Sur, I knew that as the answer. You must be at Beersmith version 3.1 to run on Big Sur. I figured you would eventually find that yourself if you looked at the 2.x FAQ http://beersmith.com/beersmith2/. So I posted my snarky reply and left.

Actually, I didn't get back to this thread for a few days as I have been fighting spammers here on the forum.  Seems spammers might be using smarter agent bots thwarting efforts top ban them. I didn't intent to leave hanging snark for too long.  OK.  Off to nuke the most recent spam post and accounts.  Oh, if you are looking or cooking site just go to ...  :o

Offline iangray

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 6
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #7 on: January 13, 2021, 03:11:21 AM »
Those notes about Big Sur are new, added yesterday. I suspected this might happen so I took screenshots. They were added because selling a commercial program for macOS as "still supported", yet knowing that it isn't supported, and won't be fixed, is...highly cheeky.

He is still doing it, but at least there is now a warning note.
« Last Edit: January 13, 2021, 04:07:31 AM by iangray »

Offline Oginme

  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 3115
  • Goats, guitars, and a home brew; Life is good!
    • Longvu LaManchas
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #8 on: January 13, 2021, 05:47:14 AM »
It definitely will not be fixed for BS2, since Brad has already announced that there will be no more development on this version of the software with the release of BS3.  To say that he is not working on a fix for BS3 to run under Big Sur is highly speculative at this time. 
Recycle your grains, feed them to a goat!

Offline iangray

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 6
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #9 on: January 13, 2021, 07:22:18 AM »
> To say that he is not working on a fix for BS3 to run under Big Sur is highly speculative at this time.

Nobody said that. BS3 appears to run fine on macOS 11.

BS2 is the program which is currently described by the website as "still supported" and I think this is a little misleading, because as you observe, it is not.

Offline jomebrew

  • Global Moderator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 1045
    • Jomebrew
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #10 on: January 13, 2021, 08:49:43 AM »
I guess I had good timing to check the FAQ.  Brad posted about this a couple months ago.  He said it was build on old libraries and will no ruin on Big Sur. He indicated 3.1 will run on Big Sur.  Somewhere else was a conversation about the M1 processor.  At that time he indicated it should run on that platform.  I haven't seen confirmation on that. I don't have a new Mac to validate and doesn't look like I will for some time if ever.

Offline BeerSmith

  • Brewer, Author, Patriot
  • BeerSmith Administrator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 5561
  • BeerSmith - take the guesswork out of brewing!
    • BeerSmith
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #11 on: January 13, 2021, 08:54:38 AM »
Hi,
  BeerSmith 3.1 does run fine on Big Sur.  Older versions have issues, so you will need to update.

  I did recently post notes on the BeerSmith 2 page noting it is not compatible with Big Sur.

  In theory BeerSmith 3.1 will also run on the new M1 chip in compatability mode, but I do not yet have a device to test it on.  I plan to order a M1 Mac shortly and I'm also working on building a universal binary for the M1 chilp.  As I don't have the device yet, I can't tell if that will be a simple recompile or require additional work.

Brad
Get a free trial of BeerSmith 3 here

Offline mjcoyne13

  • BeerSmith New Brewer
  • *
  • Posts: 1
  • BeerSmith 2 Rocks!
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #12 on: February 12, 2021, 01:25:07 PM »
Hi Brad,

I wanted to check in to see how things are looking for an M1 Mac. I currently have beersmith 2.3.7 on an older mac that works great but have purchased a new M1 air laptop that I'd like to migrate to. Before I upgrade to version 3 it would be great to know things are looking good.

I completely understand the testing and possible development time it could take, just wanted to check in!

Thanks!
Mike

Offline BeerSmith

  • Brewer, Author, Patriot
  • BeerSmith Administrator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 5561
  • BeerSmith - take the guesswork out of brewing!
    • BeerSmith
Re: 2.3.12 unusable on MacOS due to seg faults
« Reply #13 on: February 12, 2021, 11:26:00 PM »
Hi,
 Several users have reported to me that BeerSmith 3.1 will run on the M1 chip in their compatability mode.  I'm still working to compile the universal binary which should make it more efficient, but at least the current version will run on the M1 until I can get the new universal binary done.

Brad
Get a free trial of BeerSmith 3 here