Skip to content
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
This repository was archived by the owner on Mar 6, 2026. It is now read-only.

Memory spike caused by deepcopy in _QueryResult #2279

Closed
Bug
#2280
Closed
Memory spike caused by deepcopy in _QueryResult#2279
Bug
#2280
Assignees
Linchin
Labels
api: bigqueryIssues related to the googleapis/python-bigquery API.priority: p3Desirable enhancement or fix. May not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Description

@Linchin
Linchin
opened on Sep 5, 2025

See internal issue 442629997.

While calling Client.query_and_wait(), we could see a roughly 200MB memory spike, and it is caused by the helper function that processes API response triggering a deepcopy() while setting values in _QueryResult.

Image

Metadata

Metadata

Assignees

Labels

api: bigqueryIssues related to the googleapis/python-bigquery API.priority: p3Desirable enhancement or fix. May not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

Bug

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions