Repository navigation
Conversation
MainHeader, Scene.addMainHeader and Settings always appended "SofaPython3" to the plugins list. When a scene is built from a Python script (import Sofa) and not from runSofa, this RequiredPlugin loads libSofaPython3.so a second time through the PluginManager, and the process segfaults at interpreter exit.
Author
|
I also use Black formatter which may have triggered more changes in the files than strictly necessary, let me know if I should set different arguments to the formatter |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a scene is created from a Python script (
import Sofa, e.g. Gym-style environments, tests, batch simulations), the scene initializes and animates correctly but the process segfaults when Python exits (exit code 139).Loading SofaPython3 through the PluginManager (
RequiredPluginorSofaRuntime.importPlugin("SofaPython3")) seems to trigger it.A scene with no RequiredPlugin on SofaPython3 exits cleanly.
Loading SofaPython3 manually seems to be never needed:
Loading SofaPython3 twice through the PluginManager may need to raise a warning or error in SofaPython3