-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Carla 0.9.13 Segmentation fault (Bad file descriptor) #4935
Comments
@bernatx Any updates on this? |
@bernatx Any help on this? |
Any update? I've been stuck and tried to solve this issue for over a week, but got nothing further...even with carla 0.9.14 #5611 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have the same issue , any solution? |
I am experiencing the same issue. Is this already solved? |
I am having the same issue even in 0.9.15. Any suggestion? |
Hello everybody, I got a similar error code after (building and) running a package with CARLA-UE5. In my case the segmentation fault is caused by the Vulkan or GPU settings, I guess. Does somebody know a solution for this error message? |
For those in UE4 versions please share the repro steps to get this crash. We cannot do anything only with that information. We need repro steps for crashes. For UE5 ( this documentation is WIP ) https://carla-ue5.readthedocs.io/en/latest/start_quickstart/ you need at least 16GB VRAM |
CARLA 0.9.13 (docker image)
Platform: Linux
We are observing the following segfault repeatedly in our experiments with Carla:
Unfortunately we do not yet have a minimal example to reproduce and dropping all of our code here is not an option, but the crash happens quite reliably: out of 10 experiments we do, at least 3 crash after some time due to this segfault.
I don't know whether the [Line: 136] gives you any hint where the problem might lie, if not, please share some instructions how we could help you with debugging this issue.
Might be related: #3197, #3994
The text was updated successfully, but these errors were encountered: