Thu Mar 07, 2013 7:42 pm Post
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.
KB wrote:Apologies if you mentioned this already, but what is the exact computer are you running Scrivener on?
KB wrote:Also, after you completely uninstalled and re-installed Growl, did you re-download Growl or install it from a backed-up version? (Yes, I'm clutching at straws here.)
Sat Mar 09, 2013 4:58 pm Post
Sat Mar 09, 2013 5:37 pm Post
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.
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...).
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?
KB wrote:I am positive that if you test on another machine, you'll see that the crash doesn't happen.
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?
Sat Mar 09, 2013 5:44 pm Post
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.
Anyway, no other program gave me any problems with Growl...
Sun Mar 10, 2013 6:50 am Post
Sun Mar 17, 2013 7:22 pm Post
KB wrote: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.
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)?
Fri Mar 22, 2013 2:20 pm Post
Fri Mar 22, 2013 2:49 pm Post
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.)
Thu Apr 18, 2013 8:53 am Post
Thu Apr 18, 2013 11:10 am Post
In total there are 3 users online :: 0 registered, 0 hidden and 3 guests (based on users active over the past 5 minutes)
Most users ever online was 1048 on Mon Feb 06, 2012 9:07 pm
Users browsing this forum: No registered users and 3 guests