#35415: Adding content_type to StreamingHttpResponse on Linux causes memory
error
after streaming around 1GB-2GB of data.
-------------------------------+--------------------------------------
Reporter: LouisB12345 | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 5.0
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Sarah Boyce):
* resolution: => needsinfo
* status: new => closed
Comment:
Hi LouisB12345, this looks a little unusual to me as you have a sync view
calling an async function.
Maybe because of the context switching between sync and async it's waiting
for the data to accumulate before sending? What server are you running
here?
I recommend you post on [https://forum.djangoproject.com/c/users/async-
channels/23 the forum], verify that `StreamingHttpResponse` is being used
as expected, and Django is at fault here.
--
Ticket URL: <https://code.djangoproject.com/ticket/35415#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f2f8d1377-7ab3a20d-b2e9-4f09-81e2-c8ecc2bce401-000000%40eu-central-1.amazonses.com.
