Scrivener Crash: Segmentation Fault

Scrivener Scrivener for macOS
1

Hiya, it’s me again. :slight_smile: I was bouncing back and forth between iTunes and Scrivener when Scrivener crashed, so I don’t know if that contributed.

Console shows:

But I get that first error all the time.

2

I think the color picker problem might be that you have a file called .com.freeverselib in the ColorPickers folder. Because of the dot in front, it will be invisible unless you go in there with Terminal and use ls -a. I have the same thing.

The more I look into it, the more sneaky it looks. A hidden file in a folder hardly anyone ever goes into. Looks like it might be a serial number pair or something. What a dumb way to hide that information. Well, at some point you must have had a FreeVerse game installed. You can probably safely delete it if you no longer do.

Enter this into the Terminal:

rm ~/Library/ColorPickers/.com.freeverselib*
3

'k. I ran that. I’ll keep an eye on Console to see if the error appears again somehow.

But what about the Segmentation Fault? I don’t think I’ve ever had that before.

4

Keith will have to take a look at that one. The other thing is mostly likely completely unrelated.

5

The segmentation fault is nothing to worry about - it just means that Scrivener tried to access unavailable memory, most likely because it was crashing so something it thought was in memory wasn’t. You get segmentation faults when software crashes sometimes. The important thing is the crash report, which shows that the crash happened in something trying to access part of the text that didn’t exist, and the freeverse colour library reported on the console - this is a known problem; that it has crashed Scrivener for other users, and other programs too.

Thanks,
Keith