Reason 11.3 crashes on MacOS11.4 "Assertion failed: (px != 0)"

This forum is for discussing Reason. Questions, answers, ideas, and opinions... all apply.
syzygianrrf9999
Posts: 13
Joined: 14 Aug 2018

Post 06 Jun 2021

I upgraded my OS recently and am now repeatedly getting the following crash error:

"Assertion failed: (px != 0), function operator*, file /Users/buildmac/deps/boost_1_69_0/boost/smart_ptr/shared_ptr.hpp, line 728"

I've tried:
1) Reinstalling Reason
2) Reinstalling Reason, Reason Recon, and Authorizer
3) Uninstalling all of the above and then freshly reinstalling
4) Deleting preferences and application support files (see link below)
5) Partial time machine backup to MacOS 11.2
6) Disk Utility First Aid
7) Reinstalling MacOS 11.4
8) Rebooting liberally in between all of the above steps

This is the closest thing I've found to the issue just from googling: https://help.reasonstudios.com/hc/en-us ... on-Windows but this is not on Windows (I have a PC installation of Reason as well and it has had no issues so this seems to be Mac-specific and nothing to do with the version of Reason, I think) and also not using Reason as a VST/rack plug-in.

Any ideas?

syzygianrrf9999
Posts: 13
Joined: 14 Aug 2018

Post 06 Jun 2021

Code: Select all

Process:               Reason [1383]
Path:                  /Applications/Reason Suite 11.app/Contents/MacOS/Reason
Identifier:            se.propellerheads.reason
Version:               11.3.9d22 build 12405 (11.3.9d22)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Reason [1383]
User ID:               501

Date/Time:             2021-06-06 09:37:03.317 -0400
OS Version:            macOS 11.4 (20F71)
Report Version:        12
Bridge OS Version:     5.4 (18P4663)
Anonymous UUID:        F494E91D-2FEB-C16F-7D4A-B7C52B4B2D6B


Time Awake Since Boot: 310 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (px != 0), function operator*, file /Users/buildmac/deps/boost_1_69_0/boost/smart_ptr/shared_ptr.hpp, line 728.
I just tried downgrading to Reason 11.3.4 - same exact thing:

Code: Select all

Process:               Reason [1305]
Path:                  /Applications/Reason Suite 11.app/Contents/MacOS/Reason
Identifier:            se.propellerheads.reason
Version:               11.3.4d28 build 11915 (11.3.4d28)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Reason [1305]
User ID:               501

Date/Time:             2021-06-06 10:34:32.356 -0400
OS Version:            macOS 11.4 (20F71)
Report Version:        12
Bridge OS Version:     5.4 (18P4663)
Anonymous UUID:        F494E91D-2FEB-C16F-7D4A-B7C52B4B2D6B


Time Awake Since Boot: 720 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (px != 0), function operator*, file /Users/buildmac/Documents/boost_1_69_0/boost/smart_ptr/shared_ptr.hpp, line 728.

epoch
Posts: 40
Joined: 15 May 2021

Post 06 Jun 2021

syzygianrrf9999 wrote:
06 Jun 2021

Code: Select all

Process:               Reason [1383]
Path:                  /Applications/Reason Suite 11.app/Contents/MacOS/Reason
Identifier:            se.propellerheads.reason
Version:               11.3.9d22 build 12405 (11.3.9d22)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Reason [1383]
User ID:               501

Date/Time:             2021-06-06 09:37:03.317 -0400
OS Version:            macOS 11.4 (20F71)
Report Version:        12
Bridge OS Version:     5.4 (18P4663)
Anonymous UUID:        F494E91D-2FEB-C16F-7D4A-B7C52B4B2D6B


Time Awake Since Boot: 310 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (px != 0), function operator*, file /Users/buildmac/deps/boost_1_69_0/boost/smart_ptr/shared_ptr.hpp, line 728.
I just tried downgrading to Reason 11.3.4 - same exact thing:

Code: Select all

Process:               Reason [1305]
Path:                  /Applications/Reason Suite 11.app/Contents/MacOS/Reason
Identifier:            se.propellerheads.reason
Version:               11.3.4d28 build 11915 (11.3.4d28)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Reason [1305]
User ID:               501

Date/Time:             2021-06-06 10:34:32.356 -0400
OS Version:            macOS 11.4 (20F71)
Report Version:        12
Bridge OS Version:     5.4 (18P4663)
Anonymous UUID:        F494E91D-2FEB-C16F-7D4A-B7C52B4B2D6B


Time Awake Since Boot: 720 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (px != 0), function operator*, file /Users/buildmac/Documents/boost_1_69_0/boost/smart_ptr/shared_ptr.hpp, line 728.
Did you manage to fully roll back to macOS 11.3.1? If not, I suspect that Reason Studios will have to issue a point release to Reason 11 as from what you're saying it sounds like the latest macOS seems to break it; unless there's something else wrong with your system. Is everything else on your system running as expected?

syzygianrrf9999
Posts: 13
Joined: 14 Aug 2018

Post 06 Jun 2021

epoch wrote:
06 Jun 2021
Did you manage to fully roll back to macOS 11.3.1? If not, I suspect that Reason Studios will have to issue a point release to Reason 11 as from what you're saying it sounds like the latest macOS seems to break it; unless there's something else wrong with your system. Is everything else on your system running as expected?
Nope, had to go all the way back to Catalina. Not sure why though, the 11.2 backup failed so I had to wipe the disk, install Catalina, and then restore my data-only from the backup. Although that is still in progress so it remains to be seen if that worked either. Everything else was running fine.

syzygianrrf9999
Posts: 13
Joined: 14 Aug 2018

Post 06 Jun 2021

OMG.

Yeah, this isn't infuriating at all. Note the OS version. wtf is happening.

Code: Select all

Process:               Reason [6018]
Path:                  /Applications/Reason Suite 11.app/Contents/MacOS/Reason
Identifier:            se.propellerheads.reason
Version:               11.3.9d22 build 12405 (11.3.9d22)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Reason [6018]
User ID:               501

Date/Time:             2021-06-06 16:22:14.467 -0700
OS Version:            Mac OS X 10.15.7 (19H15)
Report Version:        12
Bridge OS Version:     5.4 (18P4663)
Anonymous UUID:        F494E91D-2FEB-C16F-7D4A-B7C52B4B2D6B

Sleep/Wake UUID:       5DB3808B-9F42-4B57-939B-9465C5280500

Time Awake Since Boot: 16000 seconds
Time Since Wake:       680 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (px != 0), function operator*, file /Users/buildmac/deps/boost_1_69_0/boost/smart_ptr/shared_ptr.hpp, line 728.

epoch
Posts: 40
Joined: 15 May 2021

Post 07 Jun 2021

syzygianrrf9999 wrote:
06 Jun 2021
OMG.

Yeah, this isn't infuriating at all. Note the OS version. wtf is happening.

Code: Select all

Process:               Reason [6018]
Path:                  /Applications/Reason Suite 11.app/Contents/MacOS/Reason
Identifier:            se.propellerheads.reason
Version:               11.3.9d22 build 12405 (11.3.9d22)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Reason [6018]
User ID:               501

Date/Time:             2021-06-06 16:22:14.467 -0700
OS Version:            Mac OS X 10.15.7 (19H15)
Report Version:        12
Bridge OS Version:     5.4 (18P4663)
Anonymous UUID:        F494E91D-2FEB-C16F-7D4A-B7C52B4B2D6B

Sleep/Wake UUID:       5DB3808B-9F42-4B57-939B-9465C5280500

Time Awake Since Boot: 16000 seconds
Time Since Wake:       680 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (px != 0), function operator*, file /Users/buildmac/deps/boost_1_69_0/boost/smart_ptr/shared_ptr.hpp, line 728.
How bizarre! The only thing I could think is that Apple have updated your firmware as part of 11.4 and it somehow changes the way the CPU is handled and it's that which is causing Reason to crash now irrespective of macOS version. I would have expected more complaints in this forum and RS themselves to have spotted this on their Macs if that was the case though.

Is this loading Reason with no third party REs? Do you have any hardware attached which could be causing this?

Does the standard, non-suite Reason 11.app also do this?

syzygianrrf9999
Posts: 13
Joined: 14 Aug 2018

Post 07 Jun 2021

epoch wrote:
07 Jun 2021
How bizarre! The only thing I could think is that Apple have updated your firmware as part of 11.4 and it somehow changes the way the CPU is handled and it's that which is causing Reason to crash now irrespective of macOS version. I would have expected more complaints in this forum and RS themselves to have spotted this on their Macs if that was the case though.

Is this loading Reason with no third party REs? Do you have any hardware attached which could be causing this?

Does the standard, non-suite Reason 11.app also do this?
Much as I don't want to admit it, I have a sinking feeling this is a me problem. I'm something of a Unix nerd and do a fair bit of aggressive-but-not-warranty-voiding tinkering in the terminal, and even moreso lately, as I've been very slowly dipping my toes into C and the basics-of-basics-of-coding needed to design REs. However, I've been doing that kind of thing for a few years now, and it has never broken anything before, and the only major change that occurred recently was the OS update itself, and none of this explains why a clean reinstall of an old OS with nothing but my Documents and Applications and such carried over would present the same issue, or why it would persist using Reason 11.3.4-11.3.9, and macOS10.15-11.4.

No hardware attached, I haven't tried running without third party REs (and I have hundreds of those) directly, but I think I did indirectly just via blowing away literally everything with "Reason Suite" or "Propellerhead" in the name from my entire filesystem.

I haven't tried the non-suite Reason 11... I thought suite was the standard? And then there's intro and lite...

The Reason Suite 11.3.4 reinstall I tried was the base app only, no refills or soundbanks... if that's not what you mean though, I'd love a link!

I'm impatient with these kinds of problems so last night I actually wiped my entire Mac for the Catalina restore. Since I went that far, I may as well re-attempt the OS11.2 time machine backup again... *sigh*

epoch
Posts: 40
Joined: 15 May 2021

Post 07 Jun 2021

syzygianrrf9999 wrote:
07 Jun 2021
epoch wrote:
07 Jun 2021
How bizarre! The only thing I could think is that Apple have updated your firmware as part of 11.4 and it somehow changes the way the CPU is handled and it's that which is causing Reason to crash now irrespective of macOS version. I would have expected more complaints in this forum and RS themselves to have spotted this on their Macs if that was the case though.

Is this loading Reason with no third party REs? Do you have any hardware attached which could be causing this?

Does the standard, non-suite Reason 11.app also do this?
Much as I don't want to admit it, I have a sinking feeling this is a me problem. I'm something of a Unix nerd and do a fair bit of aggressive-but-not-warranty-voiding tinkering in the terminal, and even moreso lately, as I've been very slowly dipping my toes into C and the basics-of-basics-of-coding needed to design REs. However, I've been doing that kind of thing for a few years now, and it has never broken anything before, and the only major change that occurred recently was the OS update itself, and none of this explains why a clean reinstall of an old OS with nothing but my Documents and Applications and such carried over would present the same issue, or why it would persist using Reason 11.3.4-11.3.9, and macOS10.15-11.4.

No hardware attached, I haven't tried running without third party REs (and I have hundreds of those) directly, but I think I did indirectly just via blowing away literally everything with "Reason Suite" or "Propellerhead" in the name from my entire filesystem.

I haven't tried the non-suite Reason 11... I thought suite was the standard? And then there's intro and lite...

The Reason Suite 11.3.4 reinstall I tried was the base app only, no refills or soundbanks... if that's not what you mean though, I'd love a link!

I'm impatient with these kinds of problems so last night I actually wiped my entire Mac for the Catalina restore. Since I went that far, I may as well re-attempt the OS11.2 time machine backup again... *sigh*
If you're getting that hardcore in your tweaking, I would recommend ditching Time Machine and instead using something like Carbon Copy Clone or SuperDuper! Keep a proper cloned backup of you machine and then you can easily restore or boot into your backup if you somehow bust something with your tweaking...

It sounds to me like you need to do a vanilla install from scratch of macOS to fix whatever it is you've broken at a system level.

Good luck!

Kypresso
Posts: 7
Joined: 23 Aug 2020

Post 07 Jun 2021

I know its not much consolation but i'm running the same suite version as you on a mac mini m1 with 11.4 and everything seems to be working fine.

syzygianrrf9999
Posts: 13
Joined: 14 Aug 2018

Post 07 Jun 2021

Kypresso wrote:
07 Jun 2021
I know its not much consolation but i'm running the same suite version as you on a mac mini m1 with 11.4 and everything seems to be working fine.
Yeah just my luck I'm on the final intel build of MBP.

At this point I just really wanna know what that stupid error is. For it to persist verbatim across multiple OS and software versions blows my mind a little. I know it has something to do with C++ runtime libraries(?) but beyond that, no clue. I don't even care about fixing it at this point I'm resigned to having to completely wipe and start over (my MBP is kind of a satellite of my PC anyway) I just wanna know what happened...

User avatar
dannyF
Posts: 313
Joined: 14 Jun 2019
Location: Uranus

Post 07 Jun 2021

Clown Studios strikes again.

I'm sure the work environment there is toxic.

Kypresso
Posts: 7
Joined: 23 Aug 2020

Post 08 Jun 2021

syzygianrrf9999 wrote:
07 Jun 2021
Kypresso wrote:
07 Jun 2021
I know its not much consolation but i'm running the same suite version as you on a mac mini m1 with 11.4 and everything seems to be working fine.
Yeah just my luck I'm on the final intel build of MBP.

At this point I just really wanna know what that stupid error is. For it to persist verbatim across multiple OS and software versions blows my mind a little. I know it has something to do with C++ runtime libraries(?) but beyond that, no clue. I don't even care about fixing it at this point I'm resigned to having to completely wipe and start over (my MBP is kind of a satellite of my PC anyway) I just wanna know what happened...
Have you sent the crash details to props?

  • Information
  • Who is online

    Users browsing this forum: CommonCrawl [Bot], integerpoet and 2 guests