runSofa (v19.12) crashes on Mac OSX (10.14.6)

[scharreyron]

runSofa crashes on startup on my mac. I’ve tried both v19.12 and v19.06. I’ve posted the output of runSofa at the following site (the forum tagged it as spam).

https://pastebin.com/raw/62VfHrw3

[Froy]

Hello,

Did you compile your own version? or do you try to launch the compiled runSofa.app from the sofa-framework website ?

I am on OSX 10.14.6 and the (downloaded) .app seems to work on my side, either by double-clicking it or by executing the command
$ open -a /Applications/runSofa.app

[scharreyron]

I downloaded the dmgs from your site. That’s strange.

[Froy]

(I am not related with the sofa-framework website, nor the binaries from there)

Can you try to execute the binary directly, i.e

$ /Applications/runSofa.app/Contents/MacOS/bin/runSofa

in a terminal ?

[scharreyron]

Yes that’s what I did. The output is at the pastebin link above.

[Guillaume]

Hi,

It seems that DataRepository and GuiDataRepository are not correctly initialized.
I tried on my VM with MacOS 10.14 and it worked well (like Froy).

What is your MacOS version?

[scharreyron]

Hi,

Thanks for your response. I am also on OSX 10.14.6 (cf title). How sould DataRepository and GuiDataRepository be initialized?

[Guillaume]

DataRepository is initialized with the value of SHARE_DIR and EXAMPLES_DIR taken from your-sofa-path/etc/sofa.ini
your-sofa-path/etc/sofa.ini should contain

SHARE_DIR=../share/sofa
EXAMPLES_DIR=../share/sofa/examples

Thus, DataRepository should contain your-sofa-path/share/sofa:your-sofa-path/share/sofa/examples.

GuiDataRepository is initialized with the value of RESOURCES_DIR taken from your-sofa-path/etc/SofaGuiQt.ini and the value of RESOURCES_DIR taken from your-sofa-path/etc/runSofa.ini
your-sofa-path/etc/SofaGuiQt.ini should contain
RESOURCES_DIR=../share/sofa/gui/qt
your-sofa-path/etc/runSofa.ini should contain
RESOURCES_DIR=../share/sofa/gui/runSofa

Thus, GuiDataRepository should contain your-sofa-path/share/sofa/gui/runSofa:your-sofa-path/share/sofa/gui/qt.

[scharreyron]

Ok I manually edited those files to include the paths you describe. It is still segfaulting on run though

https://pastebin.com/raw/MxBPszFr

[Guillaume]

Unfortunately your output doesn’t show any dump trace. It will not be easy to track the issue.

What was the content of all the .ini files before your edit?

[scharreyron]

cat /Applications/runSofa.app/Contents/MacOS/etc/runSofa.ini
RESOURCES_DIR=../share/sofa/gui/runSofa
SHARE_DIR=../share/sofa
EXAMPLES_DIR=../share/sofa/examples

cat /Applications/runSofa.app/Contents/MacOS/etc/sofa.ini
SHARE_DIR=../share/sofa
EXAMPLES_DIR=../share/sofa/examples

cat /Applications/runSofa.app/Contents/MacOS/etc/SofaGuiQt.ini
RESOURCES_DIR=../share/sofa/gui/qt

[Hugo]

Hi @scharreyron

Sorry for the silence of these last days, we’ve been kept busy.
Have you solved your issue?

@guillaumeparan is the above input helping understanding the issue?

Hugo

[scharreyron]

Hi,

No the issue is still there.

[Hugo]

Hi @scharreyron

Could you try launching SOFA (./bin/runSofa) from the following repository: cd /Applications/runSofa.app/Contents/MacOS

Could you tell me if you still have this issue?
In my case, the default path in the MacOS binary seems to be restricted to this one (/Applications/runSofa.app/Contents/MacOS).

Looking forward to hearing from you.
Best,

Hugo

[scharreyron]

Hi Hugo,

Both times I ran the application (see above) I ran them from that path in the terminal.

[Hugo]

I noticed Fred suggested to run a command, but I have sometime to run another one, could you test this:

$ open -F runSofa.app

Hugo

[scharreyron]

It also crashes with the following

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

[Hugo]

Hi @scharreyron

Sorry for the delay!
I know that you can still have some trace information in MacOS when a crash occurs: a “Report” will be proposed, if you agree to send the report a window opens with some additional bash information about the crash. It could help.
Could you try to copy this error report?

Best

Hugo

[scharreyron]

Hi Hugo,

Below is the trace from the crash reporter.

https://pastebin.com/raw/ejBYQwN3

[Hugo]

Hi @scharreyron

Sorry for the delay of my reply!
The crash you are undergoing is strange, it’s the first time it has been reported to us. Ensure compatibility on MacOS is actually always a bit challenging.

Could you add to your environment variables the following paths:
/path_to_runSofa.app/Contents/MacOS/share/sofa/config/default/
?

Best,

Hugo

[jnbrunet]

Hey @scharreyron,

Looking at your crash trace, the faulty one seems to be

4 com.apple.HIToolbox 0x00007fff31d80c29 _HIPersistentUICreatePersistentWindow + 69 (or the 2-3 lines before)

Searching for _HIPersistentUICreatePersistentWindow on google seems to point out different users that got similar errors. Unfortunately, they all seems to be fixing it by upgrading/reinstalling their system. Looks like an error coming from a user configuration of some sort. Do you sometime get similar crashes when opening applications other than runSOFA?

Could you try upgrading your softwares? If this doesn’t work, maybe try to compile SOFA yourself (there is a good guide here).

If it is still not working out, I guess a system update/reinstall could be needed 🙁

Unfortunately, from the quick google search and the fact that you seems to be the only one having this problem with SOFA, I don’t think we will easily find the source of the error.

If you can, keep us updated on your progress.

J-N

[scharreyron]

Hi @Hugo. I’m not too sure what you mean by “add to your environment variables the following paths.” What environment variable should be added?

@jnbrunet, thanks for looking into this. You could be right that HIPersistentUICreatePersistentWindow is the culprit. I don’t have any similar issues with any other program though, and my mac is updated regularly. Perhaps a clean reinstall of OSX would fix it, but I don’t want to do that just for this. I can try to compile from source when I get a chance. I understand that this isn’t really possible to fix on your end if you can’t reproduce the problem.

[Hugo]

Hi @scharreyron,

Sorry for my latency.
Did you try to follow Jean Nicolas’s advice ?

For your notice a new release is out, feel free to try it!

Hugo

[Author]

Posts