macOS Catalina 10.15.5 • Hacker News Board

Re: macOS Catalina 10.15.5

#101

Post by tomxor » Wed, May 27, 2020, 1:23 PM UTC

TheChaplain wrote: post #15

i2shar wrote: post #10

It's crazy that even dot releases are a full 3.6G download

Binary patching hasn't been a thing for years unfortunately. Even bigger wreck on consoles these days, where an update can be 50+ gigabytes...

> Binary patching hasn't been a thing for years unfortunately.

True, and it's fair to say binary diffs aren't worth the complexities they introduce anymore, yet the concept of only pulling updates for individual packages has been a thing for over two decades in the *nix world. It seems like a poor choice for Apple to not bother making updates more discerning while also removing binary diffs... certainly a shitty move for anyone without a 99th percentile internet connection - then again everyone outside of that group probably can't afford Apple products anyway.

For some perspective: 3.6 GiB is significantly larger than the downloads required to install my entire OS from scratch, and 36 times larger than my average weekly run of apt.

From my now outdated experience on Mac OS i'm aware they do divide things into installer packages with some kind of receipt for version info that software update probably probes. So I guess it must be that these packages are not very granular.

Re: macOS Catalina 10.15.5

#102

Post by egorfine » Wed, May 27, 2020, 1:25 PM UTC

azangru wrote: post #73

Anyone using Node.js for work who has updated to Catalina here? How did it go? I heard there were problems with node-gyp, but didn't investigate further. Everything running smoothly now? Any gotchas?

No problem with node.js and native modules development whatsoever.

Re: macOS Catalina 10.15.5

#103

Post by ryanianian » Wed, May 27, 2020, 1:27 PM UTC

MperorM wrote: post #93

Since Catalina I have been getting daily freezes, where the entire operating system locks up. I can still move the cursor around and audio keeps playing as well, but everything else is completely frozen. Once in a while the freeze lasts so long the computer crashes resulting in a crash report: Termination Reason: WATCHDOG, [0x1] monitoring timed out for service Termination Details: WATCHDOG, checkin with service: Win…

I had this happening for a while, and I tracked it down to time-machine backups starting. Every hour the backupd cronjob would trigger and I'd get a minute or so of beachball. Similar WATCHDOG termination message. It crashed a couple times and corrupted the backup database. I disabled time-machine and haven't had any freezes since.

Re: macOS Catalina 10.15.5

#104

Post by mrtksn » Wed, May 27, 2020, 1:27 PM UTC

lxgr wrote: post #94

Battery health management sounds great! I wish there was a way to customize this, though: Thinkpads have (on Linux) allowed setting thresholds for "charge only when less than" or "charge only up to" for many years now. Given that such primitives must also exist as part of 10.15.5 now, I hope that somebody will figure out how to modify the default behavior.

There's an app for that called Aldente[0]. I am sceptical of the benefits though, too much of micromanagement for a device that's supposed to just work.

I mean you can be better off if instead of undercharging the device all the time and have less than optimal charge when you need it today you can have a device that holds just as little charge some time in the feature and fix it by replacing the battery if it turns into an issue.

Live the high life today worry-free and suffer tomorrow instead of suffering today for some possible occasion in the feature where you might need few more hours of juice.

[0]: https://github.com/davidwernhart/AlDente

Re: macOS Catalina 10.15.5

#105

Post by casperb » Wed, May 27, 2020, 1:28 PM UTC

m1h4 wrote: post #31

Still having a (at least one of the multiple different) kernel panic during sleep: panic(cpu 0 caller 0xffffff801e29169c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x2754. Ever since moving to a brand new 16" MBP there isn't a day that passes wihout me being welcomed by the crash report dialog…

Same here on a 4000 euro MBP 16”. I tried everything, but multiple times a day having kernel panics when starting up from sleep in clamshell mode.

Re: macOS Catalina 10.15.5

#106

Post by brmcd » Wed, May 27, 2020, 1:29 PM UTC

logical_proof wrote: post #97

MperorM wrote: post #93

Since Catalina I have been getting daily freezes, where the entire operating system locks up. I can still move the cursor around and audio keeps playing as well, but everything else is completely frozen. Once in a while the freeze lasts so long the computer crashes resulting in a crash report: Termination Reason: WATCHDOG, [0x1] monitoring timed out for service Termination Details: WATCHDOG, checkin with service: Win…

I am! It only happens when I am on multiple monitors (clamshell opened or closed) and usually when I am in a video conference (zoom, hangouts, and G2meeting). Thought it was overheating.

Im seeming to have the same issue. 2019 MBP connecting through USB-C. However, I find the issue is less frequent (to non existent) after I switched to a USB-C to HDMI adapter.

Re: macOS Catalina 10.15.5

#107

Post by clay10 » Wed, May 27, 2020, 1:29 PM UTC

m1h4 wrote: post #31

Still having a (at least one of the multiple different) kernel panic during sleep: panic(cpu 0 caller 0xffffff801e29169c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x2754. Ever since moving to a brand new 16" MBP there isn't a day that passes wihout me being welcomed by the crash report dialog…

I've been getting these too. Extremely frustrating.

Re: macOS Catalina 10.15.5

#108

Post by 2OEH8eoCRo0 » Wed, May 27, 2020, 1:30 PM UTC

MperorM wrote: post #93

Since Catalina I have been getting daily freezes, where the entire operating system locks up. I can still move the cursor around and audio keeps playing as well, but everything else is completely frozen. Once in a while the freeze lasts so long the computer crashes resulting in a crash report: Termination Reason: WATCHDOG, [0x1] monitoring timed out for service Termination Details: WATCHDOG, checkin with service: Win…

Why do you guys put up with this? Do you like pain?

Edit: I'm not trying to troll, I genuinely want to know why people put up with this. I bounce between Linux and Windows and have no loyalty to either of them. I've settled on Windows with WSL2 on my desktop but I'm tempted again to install the new Fedora on my Thinkpad. Is it the lock in? With my hardware I can run anything I want except for macOS. Once you buy Apple hardware it seems incredibly difficult to go elsewhere.

Re: macOS Catalina 10.15.5

#109

Post by culturestate » Wed, May 27, 2020, 1:30 PM UTC

MperorM wrote: post #93

Since Catalina I have been getting daily freezes, where the entire operating system locks up. I can still move the cursor around and audio keeps playing as well, but everything else is completely frozen. Once in a while the freeze lasts so long the computer crashes resulting in a crash report: Termination Reason: WATCHDOG, [0x1] monitoring timed out for service Termination Details: WATCHDOG, checkin with service: Win…

Any time I get these they come with a bushel of IOAccelerator errors; I'm fairly sure (in my case, at least) it's a problem buried somewhere in the video decoder stack.

I can reproduce it pretty reliably by previewing a bunch of videos in Messages, and quitting the app usually solves it.

Edit: I use a 13" MBP, so that rules out most popular theories e.g. problems with the discrete GPU or graphics switching.

Re: macOS Catalina 10.15.5

#110

Post by chrisweekly » Wed, May 27, 2020, 1:31 PM UTC

dirtylowprofile wrote: post #19

Just updated my 2012 MBP. So far still alive.

My daily driver is a maxed-out (for its time) 2012 MBP15r, and I've been on High Sierra for a long time. I like the keyboard, there are maybe 5 dead pixels, and it's fast enough for my purposes. It's newrly always plugged in so the mediocre battery life hasn't been a problem. A new contract gig is about to commence, and I'll be using their hardware. It's strange to be feeling apprehension about degraded DX on a brand new dev machine vs my 8 year old warhorse.