-
Notifications
You must be signed in to change notification settings - Fork 12
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
Segmentation fault in expression starting at none:0 #129
Comments
On another set of input data, I received the following stacktrace:
|
Sorry for the incredibly late reply. Oof, this one might be beyond me. If it's giving a core dump, then it could be that the only way to get to the bottom of it is to actually inspect that, but that's something I'm not well versed at. Did you ever get things working? One thing you might test (even though it will of course take longer) would be to run it in serial. At least this way we could determine if the issue lies with multithreading. |
Vincent,
No worries-I've not been able to make progress, and as a result decided to put this project on the backburner.
I will try running the job in serial and see if there are any changes. Will come back to this shortly.
From: Vincent Landau ***@***.***>
Sent: Monday, September 4, 2023 4:30 PM
To: Circuitscape/Omniscape.jl ***@***.***>
Cc: Baecher,Joseph Alex ***@***.***>; Author ***@***.***>
Subject: Re: [Circuitscape/Omniscape.jl] Segmentation fault in expression starting at none:0 (Issue #129)
[External Email]
Sorry for the incredibly late reply. Oof, this one might be beyond me. If it's giving a core dump, then it could be that the only way to get to the bottom of it is to actually inspect that, but that's something I'm not well versed at. Did you ever get things working?
One thing you might test (even though it will of course take longer) would be to run it in serial. At least this way we could determine if the issue lies with multithreading.
-
Reply to this email directly, view it on GitHub<#129 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANPYAFG3Q5TBNHKTYNASKALXYY257ANCNFSM6AAAAAAW37AH7U>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Hi OS community,
I've been troubleshooting my analyses for some time now--getting similar issues to those described in this issue section (e.g., "task failed on specific row and column", and "AssertionError: norm(G * v .- curr) / norm(curr) < 1.0e-6").
Now that I've found a solution to these errors, my analyses are finally running longer than before--in some cases up to 90%. But now half of them are failing with the message below, and creating a core dump. I've found some mention of this on the general Julia boards, with talk of rather complicated memory allocation issues (I couldn't make any sense of it). I'm running these analyses on a computing cluster (4 cpus, 32gb ram / cpu).
Here's the full stack trace:
The text was updated successfully, but these errors were encountered: