cocoaforge

John Don wrote:

The_Tick wrote:What version of os x are you running John?

10.4.7, with latest security updates.

Was Growl installed with Adium or from the DMG?

Files left in the /tmp across a reboot will get moved to trash. Not sure why not all files do.

The_Tick wrote:

John Don wrote:

The_Tick wrote:What version of os x are you running John?

10.4.7, with latest security updates.

Was Growl installed with Adium or from the DMG?

I've played around with stuff so often over the years, that I would imagine this Growl install I have on here now was installed from the DMG.

Alright, so here's the plan. I'm going to try to get .7.5 a little after next Friday. Once that is out, we'll get you guys on it and see if that fixes it.

The_Tick wrote:Alright, so here's the plan. I'm going to try to get .7.5 a little after next Friday. Once that is out, we'll get you guys on it and see if that fixes it.

Certainly; I'd be more than happy to help.

Do the files appear when Adium (or another Growl app) is launched, when they display a notification for the first time, or after logging out and back in? (or some other condition entirely)

evands wrote:Do the files appear when Adium (or another Growl app) is launched, when they display a notification for the first time, or after logging out and back in? (or some other condition entirely)

Mine have appeared upon restarts- whether from crashes, or when I have manually restarted myself.

I'd imagine the files appearing after a crash are the result of file dumps?

Only after a crash can I reasonably reproduce these files most of the time. They appear sometimes after normal restarts as well, but the frequency is slim to none in those situations.

When the comptuer starts up, it moves the contents of the /tmp temporary folder to the trash can as 'recovered files'. I guess the behavior makes a bit of sense... anyways, Growl does the following:
1) Application X uses code within itself to begin talking to Growl. This process creates a GrowlRegDict file.
2) Application X sends Growl the information about that GrowlRegDict file
3) Growl itself (technically the GrowlHelperApp, a separate application, a single program running for all apps using growl) opens the GrowlRegDict.
4) Once it's opened, it's immediately deleted (by GrowlHelperApp).

Somehow either the (2) to (3) transition or (4) are failing.

evands wrote:Do the files appear when Adium (or another Growl app) is launched, when they display a notification for the first time, or after logging out and back in? (or some other condition entirely)

As far as I can tell from the times shown on the files, mine are created when I log off my user name - which is also when I would log out of both Adium and Growl.

MacMom wrote:

evands wrote:Do the files appear when Adium (or another Growl app) is launched, when they display a notification for the first time, or after logging out and back in? (or some other condition entirely)

As far as I can tell from the times shown on the files, mine are created when I log off my user name - which is also when I would log out of both Adium and Growl.

Hmm, I just tested this and a recovered file folder was not created when I logged out of my username, but one was created when I rebooted my computer.

For the record, I am still getting recovered files in my trash with 0.7.5.

Is it still GrowlRegDict files?

Yup.

I left Growl 7.6 off for one week - was getting the "Recovered files" folder with .growlRegDict files every reboot - had 19 of them last time.

The concern: if the Growl prefpane is deactivated, it should be *deactivated*, not firing-and-forgetting a stream of temp files in the background. The fact that a process the pane claims is deactivated is performing file-writes... well, it does not inspire trust or confidence in Growl.

If one of the other Growl-enabled applications is writing these files, I'd be happy to work with you in tracking down which one it is. However, based on the two forum threads I've read here, I'm can't tell if this problem has even been looked into seriously.

In the meantime, I'm uninstalling Growl.

We've looked into it extensively and tried to resolve it multiple times, with nothing but empty results. We have more important things to work on than this, things we can actually work on instead of poke at with pointy sticks hoping to get a reaction we want. It'll be looked at again, but I can't reproduce it and neither can a lot of people, so it's just going to take time.

If you feel it's necessary to uninstall Growl, please do. However, understand that the only reason that Growl is activated while turned off is to register Growl tickets for Applications, and then deactivated. Even in this configuration I've been unable to reproduce this issue.

I didn't mean to imply that you weren't working on Growl - for free, yet, and I appreciate that and admire the program. I just noticed that you haven't asked anyone here for any information other than OS X and Growl version number.

I'm not merely complaining, I'll help too: If you would like me to provide search for console log entries, provide example recovered files, or run some more verbosely logging build of Growl to catch the error on my system, I'll be happy to do more than just gripe.

Even if my suggestions won't help, my outsider opinion is that a bug of type "that's impossible, that process shouldn't even be running!" is a big deal.

I think it's more that it needs to be duplicatable on a development box so we can test and fix without guesswork. That said, it will be looked at a some point, but not currently.