Open buhrmann opened 6 years ago
It's exploding inside that xpc* stuff, any clue what that is?
Very difficult to find info about it, but seem like it's an Apple system library for inter-process communication.
Seems related to this on stackoverflow, but neither the option enable-threads nor threads=2 seems to have any effect.
To add some further information: the segfault occurs independently of the request library used (both requests and urllib.request), and also when the request is send to another server (e.g. google's). In other words, it seems to be a problem simply with sending any request from within the worker, no matter what kind or where to...
I am experiencing this issue too. i found this related ticket with a temporary workaround https://bugs.python.org/issue30385
Hi, When I try to send a request to uWSGI from within one of its worker processes (while processing a previous request), I get the segmentation fault below (and it doesn't seem to depend on the details of the request). When sending the request from an external process all works fine. Not sure if that's something that should be possible? If it is, would this be a bug or am I doing it wrong?
I'm on macOS 10.13.2, in an anaconda environment with python 3.6.3, uwsgi 2.0.15, and running Flask behind uwsgi.
Here's the .ini:
The uwsgi launch info:
And here the trace info: