[2.1.2] duplicate HazelHelper process after update

Updating from 2.1.1 to 2.1.2 created a second HazelHelper process that kept Hazel from operating properly until the original HH process was killed. Related messages from Hazel.log:

Code: Select all: 2007-12-06 15:42:56.067 HazelHelper[2110] Could not register server: com.noodlesoft.HazelSweeper 2007-12-06 15:42:56.073 HazelHelper[2110] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x3303, name = 'com.noodlesoft.HazelHelper.ServiceProvider' See /usr/include/servers/bootstrap_defs.h for the error codes. 2007-12-06 15:42:56.074 HazelHelper[2110] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.noodlesoft.HazelHelper.ServiceProvider) 2007-12-06 15:42:56.655 HazelHelper[2110] Could not register server: com.noodlesoft.HazelScheduler 2007-12-06 15:42:56.907 HazelHelper[2110] Could not register server: com.noodlesoft.HazelNotifier 2007-12-06 15:43:18.080 hazelfolderwatch[2116] Another hazelfolderwatch process is processing this directory. Exiting.

Did you update using the in-app system or manually? If it keeps happening let me know.

Manually updated by double-clicking Hazel in the mounted disk image volume.

Updating a running Hazel by double-clicking its icon in the mounted disk image is still problematic on 10.4.11. With 2.2.2 a few minutes ago, the typical Hazel.log messages appeared:

Code: Select all: 2008-09-25 07:51:16.156 HazelHelper[10224] Could not register server: com.noodlesoft.HazelSweeper 2008-09-25 07:51:16.178 HazelHelper[10224] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x3203, name = 'com.noodlesoft.HazelHelper.ServiceProvider' See /usr/include/servers/bootstrap_defs.h for the error codes. 2008-09-25 07:51:16.179 HazelHelper[10224] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (com.noodlesoft.HazelHelper.ServiceProvider) 2008-09-25 07:51:16.844 HazelHelper[10224] Could not register server: com.noodlesoft.HazelScheduler

Then these repeated crashes started:

Code: Select all: Sep 25 07:52:23 halo crashdump[10237]: hazelfolderwatch crashed Sep 25 07:52:24 halo crashdump[10237]: crash report written to: /Users/zzz/Library/Logs/CrashReporter/hazelfolderwatch.crash.log Sep 25 07:53:25 halo crashdump[10239]: hazelfolderwatch crashed Sep 25 07:53:26 halo crashdump[10239]: crash report written to: /Users/zzz/Library/Logs/CrashReporter/hazelfolderwatch.crash.log Sep 25 07:57:23 halo crashdump[10247]: hazelfolderwatch crashed Sep 25 07:57:24 halo crashdump[10247]: crash report written to: /Users/zzz/Library/Logs/CrashReporter/hazelfolderwatch.crash.log Sep 25 07:58:23 halo crashdump[10249]: hazelfolderwatch crashed Sep 25 07:58:25 halo crashdump[10249]: crash report written to: /Users/zzz/Library/Logs/CrashReporter/hazelfolderwatch.crash.log Sep 25 08:02:26 halo crashdump[10257]: hazelfolderwatch crashed Sep 25 08:02:27 halo crashdump[10257]: crash report written to: /Users/zzz/Library/Logs/CrashReporter/hazelfolderwatch.crash.log Sep 25 08:03:24 halo crashdump[10259]: hazelfolderwatch crashed Sep 25 08:03:25 halo crashdump[10259]: crash report written to: /Users/zzz/Library/Logs/CrashReporter/hazelfolderwatch.crash.log

Killing the HazelHelper process and restarting Hazel is the best way to ensure it's working normally again, which of course shouldn't be necessary.

Darn, it looks like that's not enough this time -- hazelfolderwatch is still crashing after the 2.2.2 update.

Could you email me a copy of the crashdump?

Also, does it still happen if you manually replace the pref pane file in Library/PreferencePanes?

Thanks.

Actually, I think I found the issue. It was a change in the last beta. I'll post back here when a fix is up.

Will the beta hopefully fix the hazelfolderwatch crashes? That's the critical problem with Hazel 2.2.2 here now. Reinstalling, restarting, removing *.hazeldb files, etc. hasn't helped.

The beta was for 2.2.2, but now that 2.2.2 final is out, the betas aren't relevant anymore.

I've uploaded a new 2.2.2 so if you re-download it, hopefully this new version should work. You'll know if you have the new version if you go to the "Info" pane and see that the build number is v483 instead of v479 (it's the part after the version number).

Let me know how it works out and many thanks for the report.

I misread your "it was a change in the last beta" comment, thinking you were going to post another one for this fix. Anyway …

The new 2.2.2 runs fine now; no more hazelfolderwatch crashes. Thanks for the quick repair!

No problem. Sorry you had to deal with this. It was an inexcusable lapse on my end but hopefully things will run smoothly from this point on. Let me know if you run into anything else.