Django Potential Fork Bomb
On 2019-05-09 14:21:15 +0530, Shakti Kumar wrote:
> On Thu, 9 May 2019 at 10:27, dieter <dieter at handshake.de> wrote:
> > Shakti Kumar <shakti.shrivastava13 at gmail.com> writes:
> > > I suspect django spawned too many child processes, and consecutively I ran
> > > out of resources on my dev server. How can I prevent this from happening?
> > > And I am not able to understand why django should spawn (if it indeed is
> > > spawning) incrementing processes with each query from the GUI.
> > I suspect the GUI to be the culprit. You have not told us what
> > kind of GUI this is: is it the (standard) GUI which comes with "Django"
> > (and runs in your browser)?
> Yes the standard GUI shipped with Django.
This may be a stupid question, but what is the standard GUI shipped with
Django? What does it do and how do you start it?
I suppose one could call the django.contrib.admin app "the Django GUI",
but that doesn't seem to fit your description that it executes code in
_ | Peter J. Holzer | we build much bigger, better disasters now
|_|_) | | because we have much more sophisticated
| | | hjp at hjp.at | management tools.
__/ | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available