Page 1 of 1

Noticed the hazel taskbar reboot?

PostPosted: Mon Oct 08, 2012 1:10 am
by HackerJL
Of late, I have noticed that when I open hazel from the top menu (click on broom, then 'open hazel'), that the icon flashes, and the log shows its starting. Is that normal, or is it crashing and restarting...

Re: Noticed the hazel taskbar reboot?

PostPosted: Mon Oct 08, 2012 11:19 am
by Mr_Noodle
It might be restarting. It sometimes happens if the running process is from the older version, for some reason. Usually that's handled when you first upgrade but maybe the process was stubborn and wouldn't quit before. In any case, I wouldn't be alarmed.

Re: Noticed the hazel taskbar reboot?

PostPosted: Mon Oct 08, 2012 11:56 am
by HackerJL
Hrm, that's not good.

Last night, did a fresh install back to lion. I set up every thing and imported my actions. I can check it every hour, and it does this.

It used to do this on 10.8, but I had other issues with Automator, so I started over on 10.7, And it is still doing it.

Thoughts?

Re: Noticed the hazel taskbar reboot?

PostPosted: Mon Oct 08, 2012 12:56 pm
by HackerJL
Actually. It does it now within seconds. And I can see with the debug turned on that it is restarting. Here is what I have:

Code: Select all
2012-10-08 10:51:20.185 HazelHelper[2536] Deregistering...
2012-10-08 10:51:20.186 HazelHelper[2536] Done
2012-10-08 10:51:20.583 HazelHelper[2550] HazelHelper v3.0.13 launching.
2012-10-08 10:51:21.170 hazelworker[2552] DEBUG: Program is licensed.
2012-10-08 10:51:21.191 hazelworker[2552] Processing folder Trash
2012-10-08 10:51:21.191 hazelworker[2552] DEBUG: Initialized
2012-10-08 10:51:21.244 hazelworker[2552] DEBUG: Pausing to wait for things to settle down.
2012-10-08 10:51:22.245 hazelworker[2552] DEBUG: Processing directories: (


...and then goes through and runs every folder its watching. And then doesnt run again...

Here is a snip from the logs showing a matched (and successful) run, and then its dead until I relaunch it:

Code: Select all
2012-10-08 09:04:41.332 hazelworker[50424] The Big Bang Theory - S05E19.mkv: Rule CLI it matched.
2012-10-08 09:04:41.333 hazelworker[50424] Hazel Alert: The Big Bang Theory - S05E19.mkv is going in to be converted
2012-10-08 09:04:41.333 hazelworker[50424] [Custom Message] Hazel Alert: The Big Bang Theory - S05E19.mkv is going in to be converted
2012-10-08 09:04:41.333 hazelworker[50424] Caught exception in rule evaluation of file The Big Bang Theory - S05E19.mkv: NSDistantObject (0x102213040) is invalid (no connection)
2012-10-08 09:04:41.333 hazelworker[50424] (
   0   CoreFoundation                      0x00007fff9166bf56 __exceptionPreprocess + 198
   1   libobjc.A.dylib                     0x00007fff8a3b3d5e objc_exception_throw + 43
   2   CoreFoundation                      0x00007fff9166bd8a +[NSException raise:format:arguments:] + 106
   3   CoreFoundation                      0x00007fff9166bd14 +[NSException raise:format:] + 116
   4   Foundation                          0x00007fff8f552030 -[NSDistantObject forwardInvocation:] + 232
   5   CoreFoundation                      0x00007fff91658fa4 ___forwarding___ + 756
   6   CoreFoundation                      0x00007fff91658c38 _CF_forwarding_prep_0 + 232
   7   hazelworker                         0x00000001000302f6 start + 190490
   8   hazelworker                         0x0000000100030330 start + 190548
   9   hazelworker                         0x0000000100014425 start + 76105
   10  hazelworker                         0x00000001000233ca start + 137454
   11  hazelworker                         0x0000000100003157 start + 5755
   12  hazelworker                         0x0000000100003d3f start + 8803
   13  hazelworker                         0x0000000100006d2f start + 21075
   14  hazelworker                         0x0000000100001b10 start + 52
)
2012-10-08 09:04:41.334 hazelworker[50424] Caught exception while getting events from scheduler: NSDistantObject (0x1020074b0) is invalid (no connection)
2012-10-08 09:04:41.334 hazelworker[50424] Could not get file events from scheduler.
2012-10-08 09:04:41.335 hazelworker[50424] [METRICS] Caught exception sending metrics to scheduler: NSDistantObject (0x1020074b0) is invalid (no connection)
2012-10-08 09:04:41.335 hazelworker[50424] Done processing folder Batch Rip TV
2012-10-08 09:05:11.421 hazelworker[1229] The Big Bang Theory - S04E06.m4v: Rule TV Show? matched.
2012-10-08 09:05:11.504 hazelworker[1229] [File Event] File moved: The Big Bang Theory - S04E06.m4v moved from folder /Users/james/Movies/Batch Encode to folder /Users/james/Movies/TV Shows.
2012-10-08 09:05:11.617 hazelworker[1230] Processing folder TV Shows
2012-10-08 09:05:11.655 hazelworker[1229] Done processing folder Batch Encode
2012-10-08 09:05:13.625 hazelworker[1230] The Big Bang Theory - S04E06.m4v: Rule Not Red? Ready to be automated! Turn Blue matched.
2012-10-08 09:05:13.628 hazelworker[1230] Done processing folder TV Shows
2012-10-08 09:05:13.739 hazelworker[1231] Processing folder TV Shows
2012-10-08 09:05:15.746 hazelworker[1231] The Big Bang Theory - S04E06.m4v: Rule If Blue, Run Automate, then turn orange matched.
2012-10-08 09:05:20.216 hazelworker[1231] The Big Bang Theory - S04E06.m4v: Rule If Orange, check tagging, then rename matched.
2012-10-08 09:05:20.491 hazelworker[1231] Done processing folder TV Shows
2012-10-08 09:05:21.142 hazelworker[2389] Processing folder TV Shows
2012-10-08 09:05:23.150 hazelworker[2389] The Big Bang Theory - S04E06-tagged.m4v: Rule If -tagged, check name, then turn orange matched.
2012-10-08 09:05:23.257 hazelworker[2389] The Big Bang Theory - S04E06-tagged-named.m4v: Rule If -named and Orange - move to itunes matched.
2012-10-08 09:05:23.352 hazelworker[2389] [File Event] File moved: The Big Bang Theory - S04E06-tagged-named.m4v moved from folder /Users/james/Movies/TV Shows to folder /Users/james/Movies/Hazel Move to Itunes.
2012-10-08 09:05:23.364 hazelworker[2389] Done processing folder TV Shows
2012-10-08 09:05:24.354 hazelworker[2397] Processing folder TV Shows
2012-10-08 09:05:26.360 hazelworker[2397] Done processing folder TV Shows
2012-10-08 10:44:03.102 HazelHelper[1191] Deregistering...
2012-10-08 10:44:03.103 HazelHelper[1191] Done
2012-10-08 10:44:03.299 HazelHelper[2453] HazelHelper v3.0.13 launching.


You see from the timestamps...nothing happened. I also turned debug on AFTER this happened, hence the lack of info.

Re: Noticed the hazel taskbar reboot?

PostPosted: Tue Oct 09, 2012 9:01 am
by flynn
I noticed that as well, running mountain lion 10.8.2. Whenever I open the preference pane, hazel seems to relaunch (when a large amount of time has passed since the last relaunch). I thought it was normal, as the relaunching seemed more or less constant but maybe I am mistaken.

Re: Noticed the hazel taskbar reboot?

PostPosted: Tue Oct 09, 2012 10:29 am
by HackerJL
Well, I can say it happens even with NO rules, or anything in hazel, so I think its by design. I was sure wondering, since I am having issues with hazel doing anything consistantly, which I am dealing with right now. I am not concerned about this anymore.

Re: Noticed the hazel taskbar reboot?

PostPosted: Tue Oct 09, 2012 11:28 am
by Mr_Noodle
Well, it's not normal. I'm not able to replicate it here but basically it only does it if the helper program on disk has been modified since it was launched. Is it possible something keeps updating the timestamp on the Hazel binaries? Also, you're not double-clicking the pref pane from the disk image every time, are you?

Re: Noticed the hazel taskbar reboot?

PostPosted: Tue Oct 09, 2012 11:36 am
by HackerJL
No, no pref pane clicking going on. Where is the location of the binary so I can check via terminal?

Re: Noticed the hazel taskbar reboot?

PostPosted: Tue Oct 09, 2012 3:44 pm
by HackerJL
I can confirm its rebooting. The pid changes everytime I close it and open it. Everything I can find in the /Library/PreferencePanes folder that relates to Hazel is timestamped for the 2nd of the month. Which I assume is compile time? Im at a complete loss of what is happening.

Any thoughts/ideas I would be fine trying/checking...

Re: Noticed the hazel taskbar reboot?

PostPosted: Tue Oct 09, 2012 8:45 pm
by flynn
I'm having a little trouble understanding what you are talking about, but all I can tell is that I am not double clicking the prefPane file.

I screen recorded what happens to show you what I mean (and apparently quicktime is not very good for screen recording, makes my computer really slow. The reboot time of hazel though is not that much shorter when I am not recording my screen).

https://www.dropbox.com/s/3ts8tsqcx1voi ... Reboot.mov

Re: Noticed the hazel taskbar reboot?

PostPosted: Wed Oct 10, 2012 12:18 am
by HackerJL
Yup, looks familiar. However, mine is a blink of an eye. And then the scripts start running again.

I also installed it on my 10.8 work macbook pro, only the demo, and it does the same thing as well. With 0 rules setup inside it. So its not just my machine at home. The problem I have is that hazel stops working all together until I restart it

Re: Noticed the hazel taskbar reboot?

PostPosted: Thu Oct 11, 2012 4:02 pm
by Mr_Noodle
Actually, I just noticed this starting to happen on my 10.8 machine (wasn't happening on earlier OS versions). I'll take a look into it but in the meantime, it should be relatively harmless so I wouldn't worry too much about it.

Re: Noticed the hazel taskbar reboot?

PostPosted: Sat Oct 13, 2012 12:40 am
by Kha
I am also having the same situation on two of my 10.8 machines.

Whenever I go to the task bar to click on the hazel icon, the app reboots and I get the "Downloaded from the internet" message. I get it every single time I click on the task bar icon, regardless of how many times I accept running the application. I think the moment I close the GUI part of Hazel, something changes in HazelHelper that makes it inactive, and get flagged for quarantine. I have noticed that this problem only started when I started using 10.8. Also, because of this, the rules do not run "in the background" as they used to.

Re: Noticed the hazel taskbar reboot?

PostPosted: Tue Oct 16, 2012 11:45 am
by Mr_Noodle
The quarantine issue is different and there's another thread on it. As for the restarting thing, I've tracked it down so it will be fixed in the next patch.