In some cases Pixyz SDK (like Scenario Processor) throws Signal 11 errors which crashes the application, there seems not to be any exceptions raised to capture this. With Scenario Processor this could often be handled on the launching application level (cleanups, reporting, etc) but if Pixyz SDK should come to real benefit we would like to have all actions in one application if possible. Is there any recommended way to catch the Signal 11 cases so the application can shut down gracefully?
I have tried to use Python’s signal to capture signal.SIGSEGV but with limited success, I have also tried to add the AtExit event handler, no success…
core.addAtExitCallback(PixyzAtExitCallback) → 1
[2024/09/09 16:59:15]
[2024/09/09 16:59:16] Exporting *.wrl…
[2024/09/09 16:59:16] Exporting *.prefab…
[2024/09/09 16:59:16] Convertion time : 16 ms
[2024/09/09 16:59:16] Writing time : 1 ms
[2024/09/09 16:59:16] Done.
last line
After core.removeAtExitCallback(PixyzAtExitCallbackID)
[2024/09/09 16:59:16] [2024/09/09 16:59:16] Error: signal received: 11
I have them on a multi-weekly basis. If you can supply a script and model to the PiXYZ guys to debug, they can do this. But in my experience the issue is hard to reproduce. Sometimes it crashes with this error, a restart later and running the exact same commands it works fine…
Hi,
Signal 11 is quite difficult to prevent or catch, it occure when the software is trying to access memory it should not try to access (for various reasons). We need to know the context in order to treat the root cause.
To do so, can you please provide the script you are executing? (including model if any) and confirm the version of the SDK you are using.
Regards
Hi @PerryscopeVG !
Would you be so kind to create a bug ticket here and share a reproducible use case (script, dummy 3D file) and your configuration?
If you already did it, please ignore!
Thanks for helping us make Pixyz better 
Hi @AxelJacquet - OK, I will, when I encounter it the next time - as said earlier it is not easy to capture with a simple example, thus me asking for any guidelines on how to catch it for a graceful shutdown.
Right now my best example is from Pixyz Studio 2024.1.0.35 (although the log belows says 2024.2.0.60…) - on one machine it results in Signal 11 on startup (always, Studio 2022 works after reinstallation), on another machine it works… a bit hard to send as a support case though
[2024/09/17 15:09:24] Pixyz Studio v2024.2.0.60
[2024/09/17 15:09:24] 16 CPU Cores
[2024/09/17 15:09:24] Session ID = wvnaefuxxfqqgnpgbybjiomnusfbcgfzlxlngdsrvjzeisvcbmfbbrbvbbmilnoh
[2024/09/17 15:09:24] PXZ_TMP_DIR is empty
[2024/09/17 15:09:24] Creating temporary directory C:/Users/..../AppData/Local/Temp/PiXYZTMP/wvnaefuxxfqqgnpgbybjiomnusfbcgfzlxlngdsrvjzeisvcbmfbbrbvbbmilnoh
[2024/09/17 15:09:24] Temporary directory created
[2024/09/17 15:09:24] Installation directory = C:/Program Files/PixyzStudio
[2024/09/17 15:09:24] Initializing XML API
[2024/09/17 15:09:24] XML API initialized
[2024/09/17 15:09:24] Initializing Network API
[2024/09/17 15:09:24] Network API initialized
[2024/09/17 15:09:24] Unable to load plugin template (Dynamic library not found)
[2024/09/17 15:09:24] Loading plugin C:/Program Files/PixyzStudio/plugins/HoopsImportPlugin/HoopsImportPlugin.dll
[2024/09/17 15:09:24] Loading plugin C:/Program Files/PixyzStudio/plugins/OdaImportPlugin/OdaImportPlugin.dll
[2024/09/17 15:09:26] Error: signal received: 11
If it helps: the next logged lines after …OdaImportPlugin.dll when it works are
[2024/09/17 15:46:17] File “C:/Program Files/PixyzStudio/plugins/HoopsImportPlugin/plugin.xml” not found !File “C:/Program Files/PixyzStudio/plugins/OdaImportPlugin/plugin.xml” not found !name ‘types’ is not defined
[2024/09/17 15:46:18] FlexLM server version : 11.16