[Bug]: Unknown-model warning flood (claude-opus-5-5) crashes the VS Code window with OOM on Windows (v2.4.0)

A user reported that an extension's warning about an unrecognized model fired for every usage record, accompanied by surging Windows renderer handles and crashes. A contributor had already opened a Claude-assisted pull request that stopped repeated warnings for the same model. The maintainer approved it, then merged a larger Codex-assisted hotfix that also recognized the model and capped other warnings. The October 5 extension release lists both patches and its completed and waived checks.

The source-level warning path has regression tests, but the team had not reproduced the reporter's Windows memory failure. A release-day request asked that person to install the new version and check warnings, handle growth and crashes. The issue remained open across a second release on October 15, with no public reporter retest as of October 20. A separate large-history stack-overflow report was closed after a different patch and release; it cannot stand in for this user's crash check.

This is an identifiable reporter-to-agent-assisted-patch-to-release chain, not requester-confirmed resolution. Some maintainer-account comments and the release prose explicitly say they were generated by an agent; account approval, merge and publish actions show release authority, not how many human minutes were spent reviewing. Keeping the original bug open preserves the missing field test instead of turning a green source check into a customer outcome.

Read at github.com · 7 min