Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

[OSX] uncaught exception of type boost::interprocess #602

Open
MrStevns opened this issue Aug 6, 2018 · 9 comments
Open

[OSX] uncaught exception of type boost::interprocess #602

MrStevns opened this issue Aug 6, 2018 · 9 comments

Comments

@MrStevns
Copy link

MrStevns commented Aug 6, 2018

Hi

I am greeted with a crashlog as soon as I start the application. This goes for both the newest release Sourcetrail 2018.3.13 and the beta release Sourcetrail 2018.3.0

libc++abi.dylib: terminating with uncaught exception of type boost::interprocess::interprocess_exception: No such file or directory

I have tried the following:

  • clearing the config folder
  • reinstalled the application
  • running as admin (sudo)

I get this from the log:

18:49:12 | 0x7fffa01663c0 | LogManager.cpp:41 setLoggingEnabled() | INFO: Enabled logging for Sourcetrail 64 bit, version 2018.3.13
18:49:12 | 0x7fffa01663c0 | SharedMemoryGarbageCollector.cpp:52 run() | INFO: start shared memory garbage collection

I'm running on Mac OS Sierra 10.12.6

@egraether
Copy link
Contributor

Can you please try rebooting. The issue seems to be related to some interprocess issue, so that might fix it.

When you say "clearing config folder", do you mean "deleting ~/Library/Application Support/Sourcetrail"?

Does the old release 2018.2.77 still work without problem?

@egraether egraether added the bug label Aug 7, 2018
@MrStevns
Copy link
Author

MrStevns commented Aug 7, 2018

Rebooting did nothing, i'm still getting same log message

When you say "clearing config folder", do you mean "deleting ~/Library/Application Support/Sourcetrail"?

Yes

I've never tried any earlier versions, I just discovered SourceTrail yesterday and was eager to try it out.
I've tested 2018.2.77 though but that too crashes.

@egraether
Copy link
Contributor

Judging by the exception the the problem seems related to shared memory:
https://stackoverflow.com/questions/39409568/boostinterprocess-ubuntu-exception-on-creating-managed-shared-memory-object
https://stackoverflow.com/questions/30850686/reasons-a-user-might-not-be-able-to-open-a-shared-memory-object-on-linux-systems

This is the first time I see this error message. Is there anything unusual about your setup? virtual machine, permissions, file system etc.?

@MrStevns
Copy link
Author

MrStevns commented Aug 7, 2018

Hmm nothing obvious comes to mind, It's a standard mac os setup, not a virtual machine.
it has default permissions as far as I remember and the file system is Mac OS Extended (Journaled)

usually i'd try to compile the application myself to see if that works but if course that's not possible here. Do you have a build with heavier logging? where is it trying to write to?

@egraether egraether added the Mac label Aug 8, 2018
@egraether
Copy link
Contributor

I have a new idea based on recent issues on some Linux distributions.

Does Sourcetrail have permission to write to ~/Library/Application Support?

@MrStevns
Copy link
Author

MrStevns commented Nov 7, 2018

it writes logs and stuff to /Sourcetrail so yeah I believe it has.

drwxr-xr-x    7 CandyFace  staff   238 Nov  7 20:55 .
drwx------+ 224 CandyFace  staff  7616 Nov  7 20:55 ..
-rw-r--r--@   1 CandyFace  staff  6148 Nov  7 20:55 .DS_Store
-rw-r--r--@   1 CandyFace  admin   995 Nov  7 20:56 ApplicationSettings.xml
drwxr-xr-x    2 CandyFace  staff    68 Nov  7 20:55 log
drwxr-xr-x    6 CandyFace  staff   204 Nov  7 20:55 projects
-rw-r--r--@   1 CandyFace  admin   977 Aug 31 14:04 window_settings.ini

@egraether
Copy link
Contributor

Then can you please try if the issue is still present in our new beta?: https://www.sourcetrail.com/downloads#beta

@MrStevns
Copy link
Author

MrStevns commented Nov 7, 2018

I just tried out the newest beta but no difference, still getting

libc++abi.dylib: terminating with uncaught exception of type boost::interprocess::interprocess_exception: No such file or directory
Abort trap: 6

@MrStevns
Copy link
Author

Just to give you an update, I upgraded to Mojave the other day, hoping that it would fix the problem. Unfortunately it didn't... the crashlog is the same.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants