#codexCrash Desktop is built with Electron: the frontend and part of the business logic run inside Chromium + Node.js (V8).
It needs to read files to build the project index / file tree / search, handle diffs and show code changes, and feed the file “context” to the agent.
If a project contains a very large dataset(e.g., in JSON format) , it can cause the Codex app to crash. That’s because Codex scans these datasets into the context, which makes the V8 JavaScript engine’s heap memory blow up. Once it hits roughly 3 GB, Codex will crash.
#codexApp
Even with the best OpenAI models available today, speaker diarization on this audio only reaches an F1 score of about 0.33.
This is just a two-speaker conversation with slightly aggressive turn-taking, yet the F1 is still not high.
#SpeakerDiarization#MachineLearning
On macOS, enabling VPIO AEC changes the system speaker volume and audio quality, and it even affects the target app’s playback. So APM is still the better choice for us. when both recording and playback are active, we can enable AEC without impacting the app’s audio output.