On the server, we were able to observe through print statements that
everything up to the render call was executing as expected. However, there
was no error to indicate what might be going wrong. We narrowed down the
likely culprit to stack overflow via the following observations:
1. If you put the contents of the included template directly in the base
template, the issue does not occur and the page renders as expected
2. If you reduce the number of instances of the include, the issue does
not occur and the page renders as expected
The desired behavior would be to at least surface some type of actionable
error message.
--
Ticket URL: <https://code.djangoproject.com/ticket/35120>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => needsinfo
Comment:
Hi, I don't think you've explained the issue in enough detail to confirm a
bug in Django. Please reopen the ticket if you can debug your issue and
provide details about why and where Django is at fault. A sample project
that reproduces the issue may also be helpful.
> 3. Force included template to be included thousands of times
Are you doing experiments? or this is a real-life scenario.
--
Ticket URL: <https://code.djangoproject.com/ticket/35120#comment:1>