Doing Elevation Evaluation, and got to the second to the last gate and

[Rob_C_Neo_2 (Robert)]

(After the Woodland Sprint gate) My M2 Mac Mini all but seized up! It was 5 to 15 seconds between screen updates, and yet Companion seemed to be working as if nothing happened. It seemed to be tracking the ride, but the data was not updating, being fed from the Zwift app apparently.

I ran Activity Monitor and it showed Zwift using 200% CPU, but I didn’t check memory. It seemed to happen nearly exactly when I crossed that one sprint gate. I found that if a started an app like FireFox, the Zwift app would run nearly normally in the background. I could fire up that app and everything would wind up to the current Companion status, but then eventually lose its grip and start stuttering, but not as bad as if it were the only app running. SO I’m wondering if I have a hardware problem, or if the Zwift app, and 15.1.1 are out having a party in high memory somewhere.

This is the first time I’ve ever experienced this issue for like years. Many years. I have videos of the seizing, but the end view of the ride showed incredible missing areas so I’d think that the chunks are likely gone on the Zwift server data as well.

If anyone needs the data, I can upload it. I’m heading to the Apple Store tomorrow, by coincidence, so could drag it along and see if they can find any issues, but then I have to go pick it up too, a 2+ hour drive.

Any ideas? Anyone want the videos?

Zwiftalizer results from yesterday’s ride…

Zwift completely ate my GPU!?!?

[Paul_Southworth (Paul)]

The one thing that occurs to me is that if you set a PR when you go through a segment banner, that will be considered a “notable moment” and trigger a video screenshot. Video screenshots can be disabled in settings.

Might be hard to tell if this helps if you can’t reliably reproduce it though.

[Rob_C_Neo_2 (Robert)]

I did not, to my knowledge, get a PR. It was my first time through that route. I’m trying to figure out what could have caused it. It looks like Zwift app ate the GPU and CPU. (Ate all time available, and only after starting another app did the macOS allow another app to take core time from the Zwift app. Eventually the Zwift app got more processor time even being the background app because it was so ‘hungry’ for time.

So is this a bug brought out by the 15.1.1 update, or is this a known issue. Having not heard fro support, it’s hard to see what happened and why.

[Rob_C_Neo_2 (Robert)]

I took the Mac Mini to the Apple Store, and they ran their diagnostics on it, and it has a clean bill of health. ‘Nothing found out of spec’.

I may have gotten a PR, but it was on the last gate, AFTER this all started going sideways and I’m not even sure of that now.

No info or words of wisdom from Zwift Support? Can someone look at the server data and see if it shows anything happening?

Thanks…