Ah - that would explain it, this problem only happens with multiple threads I believe (kinda similar to the last problem we had, except it no longer crashes, it just freezes)
If there's anything we can do to assist you with fixing this, please let me know. Cal On Tue, Feb 28, 2012 at 6:34 PM, Roberto De Ioris <[email protected]> wrote: > > > Hi Roberto, > > > > We're still having the locking issue on 1.1 latest snapshot as well, > > doesn't seem to resolve unless we use flock. > > > > Should uWSGI use flock by default for everything, or is there something > > more we can do to resolve this problem? > > The current code includes flock independently by the choosen technic (you > force it with --lock-engine flock). > > I need to make a series of tests for multithreading, i fear the deadlock > detector is not thread-safe > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
