I will try to catch it with gdb by setting watch on can_offload address. But it is possible that this was already fixed in between 1.9.3 and 1.9.6. I have my nodes on 1.9.3 and once I've upgraded one of them to 1.9.6 it stopped logging this error. I'll upgrade remaining nodes and we will see if this is really fixed.
2013/4/16 Roberto De Ioris <[email protected]> > > > I have this error on multiple nodes and different apps, so I doubt that > > this is bad memory issue. I'll do some debugging tomorrow. > > i mean process memory (not hardware memory), for some reason someone is > writing in that memory area > > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
