with gunicorn using a gevent
worker. Should I report this as a django bug?
Thanks,
Tapan
On Fri, May 20, 2016 at 3:08 AM, Erik Cederstrand <erik+li...@cederstrand.dk
> wrote:
>
> > Den 19. maj 2016 kl. 22.17 skrev Tapan Pandita <tapan.pand...@gmail.com
> >:
> >
I am running django 1.9.4 on gunicorn19.4.5 with the gevent worker
(gevent==1.0.2, greenlet==0.4.9). My app is deployed on heroku. For some
requests, I have noticed this error: "*** Error in
`/app/.heroku/python/bin/python': double free or corruption (out):
0x0403bc90 ***". I can't
We ran into this bug in our production system and spent hours debugging it
and we have our results. Looks like this is quite a major bug, at least for
us.
When we start our application on gunicorn, it spawns workers. Every request
coming to the same worker uses the same django DatabaseWrapper
even
if it was somehow possible.
On Thursday, February 27, 2014 12:38:50 PM UTC+5:30, tapan pandita wrote:
>
> I did initially think that it might have been a concurrent write messing
> with the DB but I was able to see this issue locally once where this view
> was the only one
it.
I've faced it only once locally. Logging all on our production database is
not an option since there are a lot of queries.
On Thursday, February 27, 2014 12:13:28 PM UTC+5:30, Anssi Kääriäinen wrote:
>
> On Wednesday, February 26, 2014 11:58:54 PM UTC+2, tapan pandita wrote:
>>
&
I am using transaction.atomic as a context manager for transactions in
django 1.6. There is a block of code which I want to be in a transaction
which has a couple of network calls and some database writes. I am seeing
very weird behaviour. Every once in while (maybe 1 in 20 times) I have
noticed a
Hey Guys,
We have an initial version of our product ready on Grails. However, before
we move forward, we want to make a call between using Django or Grails. The
product is basically an API and some templating. The team comprises of
people who are comfortable with both frameworks and can easily
7 matches
Mail list logo
