Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new_batch_http_request() memory leak #1217

Open
Geoge-Henry opened this issue Mar 4, 2021 · 1 comment
Open

new_batch_http_request() memory leak #1217

Geoge-Henry opened this issue Mar 4, 2021 · 1 comment
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@Geoge-Henry
Copy link

Environment details

  • Python version: python --3.6.5
  • pip version: pip --20.3.3
  • google-api-python-client version: 1.12.8

Code example

# example
from google.oauth2 import service_account
import googleapiclient.discovery

credentials =service_account.Credentials.from_service_account_info(<service_account_info>, scopes=scopes)
google_obj = googleapiclient.discovery.build(
    service, version, credentials=credentials)
request_obj = google_obj.new_batch_http_request()
for _id, request_data in request_map.items():
    product_id = request_data["product_id"]
    token = request_data["token"]
    request_obj.add(google_obj.purchases().subscriptions().get(
        packageName=package_name,
        subscriptionId=product_id, token=token),
        request_id=_id)

request_obj.execute()

While using request_obj.execute(), I found my python process happens a memory leak. use a python tool [pympler] can check the memory leak.

Thanks!

@parthea parthea added the status: investigating The issue is under investigation, which is determined to be non-trivial. label Mar 4, 2021
@parthea parthea self-assigned this Mar 5, 2021
@parthea parthea added type: question Request for information or clarification. Not an issue. priority: p3 Desirable enhancement or fix. May not be included in next release. and removed status: investigating The issue is under investigation, which is determined to be non-trivial. labels Jun 24, 2022
@Barsoomx
Copy link

for those searching, here is the explanation

#535

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

3 participants