-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StackOverflowError with curl_multi_socket_action #94
Comments
Here's a possibly-mangled backtrace I got while running one of Fredrik's download test scripts:
|
Got a trace
followed by
followed by a segmentation fault
|
So the real question is why the stack overflow is happening. Once that happens, the rest makes sense: stack overflow causes a yield, which causes libcurl to error, which leaves things in a bad state, which I guess causes a seg fault. It would, of course, be better if this error could be caught and cleaned up, but that's hard since the callback has to throw the error asynchronously. |
Line 349 is this: |
Also: verify that that's the right line on whatever version is actually running. It's changes a bit in recent versions. |
Guess the next thing here is to see if #102 fixed it. |
Any further sign of this since #102? |
Closing, presumed fixed. |
I believe this problem is still present. I have some code that runs fine under Julia 1.5 and errors under Jula 1.6 with the following error: |
Ok, so this issue is a duplicate of #110 — or rather vice versa, but that issue has more details so let's leave that one open. |
This is a pretty low quality bug report since a lot of stacktraces were suppressed by try-catch, but I think the origin is a StackOverflow in Downloads. My logs only show
after a
Downloads.request(...)
call and then the logs were filled with 1.3 million lines ofI have now put in some more debugging statements so hopefully it happens again and I will have more information...
The text was updated successfully, but these errors were encountered: