Skip to content

fix(lib): prevent memory leak by removing TypeVar subscript in construct_type_unchecked (#3084)#3091

Open
cloudyun888 wants to merge 1 commit intoopenai:mainfrom
cloudyun888:fix/responses-memory-leak-3084
Open

fix(lib): prevent memory leak by removing TypeVar subscript in construct_type_unchecked (#3084)#3091
cloudyun888 wants to merge 1 commit intoopenai:mainfrom
cloudyun888:fix/responses-memory-leak-3084

Conversation

@cloudyun888
Copy link
Copy Markdown

Summary

When using client with structured outputs, is called with TypeVar-subscripted generics like . Since is an unresolved module-level TypeVar at runtime, Pydantic cannot resolve it, causing to always return . This prevents caching, allocating a new / (heavy Rust objects) on every call — a unbounded memory leak.

Changes

  • Replaced with
  • Replaced with
  • Replaced with

Non-parameterized base classes resolve correctly at runtime and Pydantic can cache their schemas.

Testing

Run a workload with structured outputs under memory profiling. Before fix: unbounded growth of SchemaValidator objects. After fix: stable memory usage.

Fixes #3084

…uct_type_unchecked

Pydantic model_rebuild fails for TypeVar-subscripted generics like ParsedResponse[TextFormatT]
because TextFormatT is unresolved at runtime. This causes model_rebuild(raise_errors=False)
to return False on every call, preventing _built_memo caching and allocating a new
SchemaValidator/SchemaSerializer on every parse_response() call.

Fix: use non-parameterized base classes (ParsedResponseOutputText, ParsedResponseOutputMessage,
ParsedResponse) which Pydantic can resolve at runtime.

Fixes openai#3084
@cloudyun888 cloudyun888 requested a review from a team as a code owner April 15, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Async Responses Structured Outputs Memory leak

1 participant