Another hazelworker process is processing folder (null).

[darkskyz]

Hi,

Since I installed OS X 10.8, I have had problems with rules not working in Hazel.
I am now running Hazel 3.0.12 on 10.8.1 and I use (for example) Hazel to sort pictures into subfolders using EXIF date taken metadata and videos using file date created. Nothing too fancy and it used to work.
Now when I had pictures to the folder and Hazel triggers its rule, I often (not always though) experience a non working action on the files and I get the following error in the log :
"Another hazelworker process is processing folder (null). Exiting."

Searching the support forum I have seen that you recommend rebooting in such a case. Sure it solves the problem for the said files but it happens again after a while and I need to keep this Mac on as much as possible for tons of reasons so this is not a suitable solution in my case.

Would you have any idea of a solution for this problem that does not mean rebooting the computer as this defeats the purpose of automating things on it doesn't it ?

Thanks in advance.

Nicolas

[Mr_Noodle]

If another process is running that means, well, another process is running. You need to look at the logs to see what that process is doing. I can't say what it is without seeing those.

[daveblademan]

also getting this issue - takes about 1-2 days after rebooting for it to appear. Running on 10.8.2, Mac Mini (headless).

Also found the crash log .. abbreviated but attached below (let me know if you need the full log)

Process: hazelworker [5637]
Path: /Library/PreferencePanes/Hazel.prefPane/Contents/Resources/hazelworker
Identifier: hazelworker
Version: 3.0.12 (865)
Code Type: X86-64 (Native)
Parent Process: HazelHelper [5375]
User ID: 501

Date/Time: 2012-09-24 16:49:54.292 -0700
OS Version: Mac OS X 10.8.2 (12C54)
Report Version: 10

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

VM Regions Near 0x18:
-->
__TEXT 0000000100000000-0000000100061000 [ 388K] r-x/rwx SM=COW /Library/PreferencePanes/Hazel.prefPane/Contents/Resources/hazelworker

Application Specific Information:
objc_msgSend() selector name: release
objc[5637]: GC: forcing GC OFF because OBJC_DISABLE_GC is set

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff90a8b750 objc_msgSend_vtable14 + 16
1 com.apple.AutomatorFramework 0x00007fff8d134e2f -[AMWorkspace setError:] + 65
2 com.apple.AutomatorFramework 0x00007fff8d134f7e -[AMWorkspace runWorkflowAtPath:withInput:error:] + 76
3 hazelworker 0x0000000100013979 0x100000000 + 80249
4 hazelworker 0x000000010002350e 0x100000000 + 144654
5 hazelworker 0x00000001000034d3 0x100000000 + 13523
6 hazelworker 0x00000001000041a3 0x100000000 + 16803
7 hazelworker 0x0000000100006f0b 0x100000000 + 28427
8 hazelworker 0x0000000100001e8c start + 52

Regards
Dave

[Mr_Noodle]

It is much better if you email stuff like this in. I believe there should be a bit more info underneath what you pasted. Click the "Contact support" button in the Info section and attach the full dump. Also, include whatever Automator workflow you were using there.