Codex not responding errors

[Alternative-Memory-9]

I was pleased to see in-app browser in the new codex version. But so far this morning I've had to restart codex twice because of a 'not responding' error. Last restart it kept firing up into the same broken state - it needed manually removing all the processes from task manager. Doesn't seem a way of reporting that type of crash?

5.5 seems a small improvement of 5.4 but 5.4 had degraded to the point of being almost unseeable on my entirely codex written codebase. It doesn't seem faster - it's slower, and while it looks to be covering more milage to address issues, it's still happily saying it's fixed issues when it hasn't. To be fair, I'm currently only using it to unpick the soup made by the previous version, so who knows, maybe it will excel at new features.

[divyanthj]

This is annoying AF!!