I'm going to be testing too today, will let you know if I can get it to crash - was quite easy to do with 10.15.2...
I wonder how many logic-boards have been replaced because of the software issue ?...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Catalina 10.15.2 freezes/crashes MBA every single day – am I alone?
- Thread starter VSG
- Start date
- Sort by reaction score
I'm going to be testing too today, will let you know if I can get it to crash - was quite easy to do with 10.15.2...
I wonder how many logic-boards have been replaced because of the software issue ?...
Mine has had 10.15.3 on since yesterday evening - both that and my iMac Pro were suffering with this quite a lot. I shall report back as both are in fairly heavy use here.
So I just finished installing the new update (10.15.3). I put the MBP to sleep, and guess what, it crashed again. This is bulshit, I'm going to get a replacement. Total waste of time and effort, and now I need to go deal with those "genius" guys and convince them that I got a lemon.. Sigh..
Oh bugger.
EDIT: I ran a couple more tests and it seems all shares I mount on my Airs are now capable of surviving a sleep/wake event, whether it is triggered by closing the lid or selecting "Sleep" from the menu. No crashes.
EDIT: I ran a couple more tests and it seems all shares I mount on my Airs are now capable of surviving a sleep/wake event, whether it is triggered by closing the lid or selecting "Sleep" from the menu. No crashes.
Last edited:
Hi,
just to be clear, hwojtek, can you resume the actions taken on your side to ensure that the mountpoints will be clean enough not to freeze Catalina on wakeup ?
Then, the users of this OS − who dont want to rollback to Maverick− will have a clear process to use SMB/AFP shares?
Tks!
just to be clear, hwojtek, can you resume the actions taken on your side to ensure that the mountpoints will be clean enough not to freeze Catalina on wakeup ?
Then, the users of this OS − who dont want to rollback to Maverick− will have a clear process to use SMB/AFP shares?
Tks!
Well, I can report that both my iMac Pro and my 16" MBP have not crashed at all since the 10.15.3 release - the previous BETA it did crash on, so something changed with the public 10.15.3?
What I just did seconds ago was mounting three shares using SMB and opening three files (one from each) in respectively Excel, Preview and BBEdit, then selecting "sleep" from the Apple menu. Now I will wait 10 minutes and update the post.
UPDATE: all works perfectly well. All the apps were able to continue without any errors. No kernel panics, everything works as intended.
Last edited:
I can also confirm that with 10.15.3 the problem no longer exists. I have Automounter up and running again since Tuesday evening and no more Finder crashes. Sleep/wake works as it should again. I think the update of smbfs.kext from 3.4 to 3.41 has been the key to solve the problem.
I haven't been able to replicate this problem using AFP on 10.15.2 - in fact I switched temporarily to AFP to avoid the erroneous SMB behavior and haven't had any issues with AFP.
That's disappointing to hear. Personally I've had zero issues now since the public release of 10.15.3.
Nope. Not with Synology 5.2.
In fact, I think the problem is linked to SMB 1/2, and Synology previous to 6.1 cannot completely disable SMB 1 or 2.
Neither it permit to disable AFP… or do any backup with Time Machine over SMB.
This is a joint failure between syno/apple… and a pity, because changing a NAS is not the same cost as upgrading a macbook…
In fact, I think the problem is linked to SMB 1/2, and Synology previous to 6.1 cannot completely disable SMB 1 or 2.
Neither it permit to disable AFP… or do any backup with Time Machine over SMB.
This is a joint failure between syno/apple… and a pity, because changing a NAS is not the same cost as upgrading a macbook…
I've had the same issue: 2015 MBA would freeze at random times since upgrading to Catalina. Updated to 10.15.3 a few days ago. It does not appear to random freeze as I work anymore, but I now find my MBA dark and frozen every morning (left plugged in, lid open).
The only applications visibly running were Chrome with several AWS tabs, and a couple of terminal windows ssh'd to a Raspberry Pi (working on an Alexa + IoT device). I do not have any external mounts or shares of any kind.
Last night, I killed everything (Chrome, terminals, Mail, cloudphotod) and this morning my laptop is alive and well (and cloudphotod is back). Will start experimenting with various apps left running overnight and report if/when I find a probable culprit.
The only applications visibly running were Chrome with several AWS tabs, and a couple of terminal windows ssh'd to a Raspberry Pi (working on an Alexa + IoT device). I do not have any external mounts or shares of any kind.
Last night, I killed everything (Chrome, terminals, Mail, cloudphotod) and this morning my laptop is alive and well (and cloudphotod is back). Will start experimenting with various apps left running overnight and report if/when I find a probable culprit.
This sounds like a different freeze that I've had reports of - is it a hard freeze where not even the mouse moves?
If so, then I think I've tracked that down to graphics card switching, for example when something in Chrome/Safari requires the higher performing graphics card, it will switch and crash..
Had this exact same issue in 10.10 and 10.11 until 10.11.3 - seemed to come back with 10.12 and go away again...and now seems to be back in 10.15...
If so, then I think I've tracked that down to graphics card switching, for example when something in Chrome/Safari requires the higher performing graphics card, it will switch and crash..
Had this exact same issue in 10.10 and 10.11 until 10.11.3 - seemed to come back with 10.12 and go away again...and now seems to be back in 10.15...
Sounds like the graphics card switching issue - used to do it a lot when flash was installed - this day and age no need for flash - if you have that installed try removing it and see how you get on.
And as I say this was down to the graphics card switching between the high performance one and the discrete one - flash would always try to get the higher performing one...
And as I say this was down to the graphics card switching between the high performance one and the discrete one - flash would always try to get the higher performing one...
It won't be while you're using it as it will be on the higher performing graphics card, it will be when it gets a sniff of switching from the discrete to the higher performing graphics card that it will crash - could just be something as simple as an advert on another page that triggers it.