#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
-------------------------------+--------------------------------------
Comment (by LouisB12345):
Replying to [comment:2 Sarah Boyce]:[[br]][[br]]Hello Sarah,[[br]][[br]]I
know for sure that the data is not accumulating before sending, because
the download starts immediately. If i where to not call an async function,
then you will notice the delay and see that it loads the entire file in
memory. Also this would not explain why the memory-error does not happen
when i leave out the content_type.[[br]][[br]]The server I am running is a
'''''Proxmox''''' vm running '''''Debian12''''' with '''''4 cores''''' and
'''''4GB ram''''', '''''intel-core i5-6500T'''''.
--
Ticket URL: <https://code.djangoproject.com/ticket/35415#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f3356ce4b-743d4aa3-4b05-4d92-b5af-cbf00f0cde7d-000000%40eu-central-1.amazonses.com.
