KB wrote:Okay, I'm now officially baffled. I've just fired up the 2.3.1 code base to look at what has changed regarding Growl, and there is nothing. 2.3.1 and 2.4 use the same version of Growl and the same code calling on it. Moreover, the crash log seems to indicate that the crash is coming from the Growl framework rather than from Scrivener itself.

yes, it looks like it comes from the growl framework.

KB wrote:Apologies if you mentioned this already, but what is the exact computer are you running Scrivener on?

I recommend sticking with the "legacy" 10.4+ version for now. The features are identical, the only difference being that it doesn't contain the Retina display graphics (which you don't need on your MacBook anyway) and you have to use the workaround the first time you open it to bypass GateKeeper. Clearly there is something very odd going on with Growl on your machine, but to be honest I don't really know how to troubleshoot this next (I don't think I've said that before...). Because the crash is coming from inside an external framework (Growl) and not from inside Scrivener, and because we don't have a single other user with this same crash, it is very difficult to guess at the cause of this. The only difference I can think of between 2.3.1 and 2.4 - given that they incorporate the same Growl framework and the same code invoking Growl - is that 2.3.1 was, I think, built on Lion, whereas 2.4 was built on Mountain Lion. I can't think of a reason that would make a difference, though. I've been scouring Google trying to find crashes like yours, and there are a few (with Growl in general, not in Scrivener), but with no resolution other than updates to the Growl framework, and yet you are using the latest. Do you have another computer at all? I am positive that if you test on another machine, you'll see that the crash doesn't happen. Just one more check - have you double-checked that there are no other versions of the Growl framework, older versions, lurking in the root /Library/Frameworks folder, or somewhere similar?

KB wrote:I recommend sticking with the "legacy" 10.4+ version for now. The features are identical, the only difference being that it doesn't contain the Retina display graphics (which you don't need on your MacBook anyway) and you have to use the workaround the first time you open it to bypass GateKeeper.

That's what I will do as a solution for the time being.

KB wrote:Clearly there is something very odd going on with Growl on your machine, but to be honest I don't really know how to troubleshoot this next (I don't think I've said that before...).

yes, it looks like a rare thing, but I have not installed anything fancy that would interfere with Growl.

KB wrote:Because the crash is coming from inside an external framework (Growl) and not from inside Scrivener, and because we don't have a single other user with this same crash, it is very difficult to guess at the cause of this. The only difference I can think of between 2.3.1 and 2.4 - given that they incorporate the same Growl framework and the same code invoking Growl - is that 2.3.1 was, I think, built on Lion, whereas 2.4 was built on Mountain Lion. I can't think of a reason that would make a difference, though. I've been scouring Google trying to find crashes like yours, and there are a few (with Growl in general, not in Scrivener), but with no resolution other than updates to the Growl framework, and yet you are using the latest. Do you have another computer at all?

I do have another computer, but it's still on 10.6.8 because it cannot run 10.8. - so I think that won't really help.

KB wrote:I am positive that if you test on another machine, you'll see that the crash doesn't happen.

sure, otherwise it would be easier to reproduce for you.

KB wrote:Just one more check - have you double-checked that there are no other versions of the Growl framework, older versions, lurking in the root /Library/Frameworks folder, or somewhere similar?

I'll have a look and tell you later. I actually HAD growl installed before it was updated and went to the App Store. Even though I thought I deinstalled everything, I'll have a (more thorough) look again. Anyway, no other program gave me any problems with Growl...

frofa wrote:I'll have a look and tell you later. I actually HAD growl installed before it was updated and went to the App Store. Even though I thought I deinstalled everything, I'll have a (more thorough) look again.

Great, thanks.

Anyway, no other program gave me any problems with Growl...

I do understand that, but that doesn't necessarily mean that the problem lies in Scrivener.

By the way, I notice that the crash reports you posted here all come from user id 502, which is the second user on the machine - I assume you've already tested this, but what happens when you run from the admin account (the first user account, with id 501)?

Just as a note, Growl can be a little messy to uninstall, so depending how you did it you may not have cleaned up all the files it scatters. There's a page on the site with steps for getting everything cleared out here: http://growl.info/documentation/growl-p ... emoval.php You may have already done it, but it's worth taking a look and will help indicate places Growl may have created files.

frofa wrote:I'll have a look and tell you later. I actually HAD growl installed before it was updated and went to the App Store. Even though I thought I deinstalled everything, I'll have a (more thorough) look again.

Great, thanks.

so, after a "look again" and also consulting the Growl homepage, I am absolutely sure that Growl is fully de-installed. All Growl-related files are also gone, but to no avail. I have since re-installed Growl again (which also did not help, of course, but I wanted Growl back).

KB wrote:By the way, I notice that the crash reports you posted here all come from user id 502, which is the second user on the machine - I assume you've already tested this, but what happens when you run from the admin account (the first user account, with id 501)?

This is strange! The main differences between the MAS and regular version are:

1. The MAS version is sandboxed. This is unlikely to be affecting things here, though, as sandboxing generally causes issues rather than prevents them.

2. The MAS version does not contain the Sparkle or eSellerate frameworks. However, again, that's unlikely to be causing the issue since there is no indication from your crash logs that these are in any way at fault here.

3. The MAS version strips all PPC symbols from the Growl framework, since MAS apps must contain only Intel binaries.

Given that your crashes seem to be coming from Growl, I wonder if (3) is the deciding factor here?

Here's something to try: Ctrl-click on the MAS version, select "Show Package Contents", and drill down into the /Contents/Frameworks folder. Copy the Growl.framework. Then do the same with the regular version that is crashing for you, and replace the Growl.framework in that with the one from the MAS version. Then try running the regular version - does it work? (If it doesn't, please post the crash report if it's different - it is possible that the code-signing differences between the two versions will cause it to fail anyway.)

KB wrote:Then try running the regular version - does it work? (If it doesn't, please post the crash report if it's different - it is possible that the code-signing differences between the two versions will cause it to fail anyway.)

I now tried the framework "transplantation", but still the regular program crashes. Here is the crash report:

I have got a consistent crash behavior of scrivener. It happens when using the find and replace in the project. I can send you the project that does that for you to test (it is a very small one). I just want to find 3 words and replace then with 3 other words in all the project but it is not working (progress bar not advancing) or more often, crash… (I sent you the log crash a few days ago. I was away and got back so I retried it hopng it would work but it still crash…

Please tell me what you think…Thank you in advance,

All the best,

Loïc

PS : I have just tested it with a new project from my custom template : same crash…

I'm afraid someone beat you to this one, but thanks for reporting it! This is down to the RegEx code that was added in 2.4, which, although not available on 10.6, is still causing a crash. I've already fixed this for the next update and will have a public beta out in the new week or so.