[BUG] Segmentation fault at 0x0000000000000000 Citadel (Fortress too now) #1100
Comments
|
What are you trying to load? It looks like it's an unsupported plugin. Also, please copy logs instead of pasting screenshots, because we can't search for text inside images. |
|
Just the regular sdf file I've been using. Everytime it crashed, I just re-launch it and it worked. It just happens sometimes.
The log looks like this: It is really hard to reproduce steps since it always occurs at random time. Please let me know if this log doesn't provide sufficient information. I will import it to log.txt everytime I launch ign. |
That plugin isn't currently supported, see gazebosim/ros_gz#40
That's important information to reproduce your setup. When you provide your environment information, it's good to also explain that you're using ROS, what version of ROS, and how you installed It will be difficult to help you without more information, like a backtrace. Your problem could be coming from anywhere: Gazebo, ROS, your own setup... |
|
Ah, gotcha! I overlooked the part where it says That explains a lot! I'm using Foxy, 20.04 and Citadel. I will sure to add it on any bugs in future with more detail information. I'm closing this since this is something I can fix on my end by either replace it or remove it. Thank you very much for your time! |
|
Hi there again, I removed the point cloud plugin from the file and ran it. It crashed without using that unsupported plugin. The log on terminal (I will try again to get a full log text file shortly) The log on terminal:[ign gazebo-1] 7f4b9424a000-7f4b942cd000 r--p 00000000 103:02 6949383 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8 Information about my enviroment and setupOS: Ubuntu 20.04 ROS2 Version: Foxy Steps to launch the ign:
When will it crash?: This is the issue since it is very random. Sometimes right at the start, sometimes 3 minutes later, and sometimes way later. Once it crashed, just re-launch it and it will be good until you exit the program. This doesn't happen on our model only. It happens to tutorial, test models from fuel tools and open our model on local/docker. |
|
I got the full log by This has over 2k lines. from line 1 to line 9 is what it looks like without crash. After that, it's the crash output. I hope this brings you useful and helpful information! |
|
We have a open source github but it is still under development by Neuraville team. If you want to see the bug for yourself, you can do so by following the steps:
This is designed to set things up immediately for new users too :) I hope this helps a lot too as well! I wanted to make sure you aren't having any hard time I just wanted to clarify this part. I wanted to confirm with the crash bug only. This crash is just random for my team and me. The full log above captured the full log after I import it to the fulllog.txt |
|
Update: This is also a bug on Fortress as well too. :( |
Crash on Fortress suddenlyIt crashed on me just like it did to Citadel. Which leads to here issue The log:
I'm still unable to reproduce this bug since it's also random. This was my 8th launch. There was no crash prior to this. |
Kakcalu13
changed the title
|
Hi @Kakcalu13 , thank you for all the information. I'm struggling to find actionable information on the provided logs though. Thank you for providing instructions about your how to reproduce your setup. Unfortunately I don't have enough time to test out your full setup in depth. Ideally, we'd be able to create a minimal example to reproduce the issue so we can pin-point the culprit. I suspect you may be running into GUI issues like #721 and #722. |
|
Thank you for the reply. Those issues you mentioned are the same issue as this. I'm closing this issue to reduce the amount of same issues. I will follow those issues! It's hard to create a minimal example to reproduce the issue since it's very random. Thank you for your time! :) |
Environment
Reproduce the step to create an issue:
Unable to reproduce. It just happens randomly.
full log:
fulllog.txt
The log above is from the local. The screenshot below is from the docker:
Is this known bug? Is there any workaround for this at the moment?
Also without the error should look like this (highlight only):
The below section (non-highlight) is a bug.
The text was updated successfully, but these errors were encountered: