You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a contrived (but important) test, simply running yes has the following results:
Mac mini, 16GB RAM: Keeps up alright for a few minutes, before crashing with what feels like an OOM; 200%+ CPU (main thread and terminal queue both 100% busy)
iPhone 12 Pro Max: Runs for about 1 second, then terminal screen goes blank for about 1 second, then crashes
Of course, this is unacceptable performance. Terminal, iTerm2, GNOME Terminal, Mintty, Windows Terminal, likely even NewTerm 2 (iTerm1) can all handle this without issue as long as the buffer size isn’t set too crazy high. Specifically the same test with iTerm on the same Mac ran fine for 10 minutes with ~150% CPU usage. I think we’re definitely capable of getting the CPU usage down to at least 150% (100% main thread redrawing the UI 60 times a second, plus 50% on parsing), without crashing for any reason ever.
Incredibly annoyingly, the iOS issue seems to not generate a crash report! It leads me to believe it’s a very quick OOM or excessive CPU use watchdog kill. That should still generate a watchdog/runningboard report, yet, I’ve cleared out all crash reports so I don’t miss it and nothing is appearing under Analytics Data. Literally nothing useful in Console either! First it started falling over, and then it fell over.
macOS does generate a crash dialog, so that crash report is below. I expect fixing this will improve most or all of the iOS issue anyway.
As a contrived (but important) test, simply running
yes
has the following results:Of course, this is unacceptable performance. Terminal, iTerm2, GNOME Terminal, Mintty, Windows Terminal, likely even NewTerm 2 (iTerm1) can all handle this without issue as long as the buffer size isn’t set too crazy high. Specifically the same test with iTerm on the same Mac ran fine for 10 minutes with ~150% CPU usage. I think we’re definitely capable of getting the CPU usage down to at least 150% (100% main thread redrawing the UI 60 times a second, plus 50% on parsing), without crashing for any reason ever.
Incredibly annoyingly, the iOS issue seems to not generate a crash report! It leads me to believe it’s a very quick OOM or excessive CPU use watchdog kill. That should still generate a watchdog/runningboard report, yet, I’ve cleared out all crash reports so I don’t miss it and nothing is appearing under Analytics Data. Literally nothing useful in Console either! First it started falling over, and then it fell over.
macOS does generate a crash dialog, so that crash report is below. I expect fixing this will improve most or all of the iOS issue anyway.
The Mac crash report
The text was updated successfully, but these errors were encountered: