top | item 29142667

(no title)

mstange | 4 years ago

For people who are experiencing a leak on macOS 12: Check if you have set a custom cursor color in the system accessibility preferences. Resetting the cursor color to the default may fix it.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1735345#c18

(edit: rephrased to mention macOS 12)

discuss

order

2bitencryption|4 years ago

Good lord would I love to see the postmortem breakdown on that one

valleyer|4 years ago

Having worked at Apple adjacent to the likely responsible teams, the relevant details are: overworked engineering teams, insufficient QA investment, and most of all a yearly macOS major release schedule that persists primarily to benefit the egos of Apple's upper management.

Until you see a WWDC that doesn't announce a major release of macOS, expect more of the same.

To any involved Apple folks here, I feel your pain, and I'm sorry.

nodejs_rulez_1|4 years ago

Whatever that is, it's definitely not a binary tree inversion bug.

M4v3R|4 years ago

You're right, I've just checked and when I set my cursor to be a custom color in accessibility settings suddenly my Firefox started to eat up memory as crazy :D. This went away as soon as I reset the cursor to default colors.

thih9|4 years ago

That’s a nice catch, must have been satisfying to find this.

Also, it seems like a relatively easy memory leak to fix, hopefully in an upcoming OS update.

Looking forward to the fix.

masklinn|4 years ago

The author is specifically noting they're on Big Sur so they should not be affected by this.

mstange|4 years ago

Oh, you're right. I missed that.