Closed pawelbudziszewski closed 2 weeks ago
This is not a problem of ROS 2 Gem, but the problem of Gem management within O3DE. This issue was raised by me recently here: https://github.com/o3de/o3de/issues/18363
Ok, I see, thanks. From the "o3de-extras" point of view, IMHO we should add a relevant note in the README. @jhanca-robotecai feel free to close this issue if you think it's not needed.
This problem is user's fault. There is clear error message in Editor.log https://github.com/o3de/o3de/pull/18253. This issue is duplication of resolved https://github.com/o3de/o3de/issues/18234.
I closed the issue due to the duplication. However, I do not agree with the statement that this problem is the user's fault - adding a Gem to the empty project (ROS 2
Gem in this example) should not cause a crash. Message in logs helps to debug the problem, but we still need a solution that ensures there is nothing to debug.
Describe the bug In the stabilization branches of O3DE and Extras: when I create a new project using the default O3DE template and add the ROS2 gem, I have a segfault when launching the Editor. This is caused by the fact, that the default template includes PhysX 4 gem, while ROS2 gem includes PhysX 5 (in the same time). This can be fixed easily by removing the
PhysX
gem from theproject.json
(or changing it toPhysX5
). However, diagnosing the problem is extremely hard, even for experienced users:At the same time, I can't see any information about this problem and the solution in the ROS2 gem README.
IMHO using the default template to create a ROS2 project may be a common practice. This is what I usually do when I don't need all the assets from robotic templates in my project. This issue, together with a fix should be at least described in the ROS2 README. This is the fastest solution, but in general, applications shouldn't crash in such cases.
Assets required n/a.
Steps to reproduce Steps to reproduce the behavior:
ROS2
intoproject.json
Expected behavior The application should inform about the problem. Maybe even during compilation
Actual behavior Crash without any information which would help to spot the problem
Screenshots/Video n/a
Found in Branch stabilization/2409
Commit ID from o3de/o3de and o3de/o3de-extras repositories ed3d36f354f2b75a45aa44d2fbf384f49531108b
Desktop/Device (please complete the following information):
Additional context Debugger backtrace: