1.3.3 development/watch mode hogging cpu

[generationfourth]

I was running 1.2.1 (on accident) for a while and the live updating with development/watch mode was working really smoothly. After I updated to 1.3.3 and I have watch mode running my code editor, espresso, jumps to 50-90% of my cpu. Basically it's unusable now.

It seems to be any version from 1.3.1+. I'm not sure if this is the right spot for this but I'm getting desperate and was wondering if anyone had similar problems. I do not understand .js so I do not know how to trouble shoot.

thanks

[lukeapage]

Is this watch mode in the browser? And does the high cph usage come from
your browser or editor? All the time or just when you make changes?

[generationfourth]

It is occurring in the editor- Espresso has a built in preview browser. When using less.watch() script in the head cpu usuage spikes up and slows down the editor to the point where I can barely use it. If I deactivate the script the cpu usage goes down and the fans will turn off eventually. When I was running 1.2.1 less.watch() worked perfectly fine.

I can't seem to get the less.watch() script to work in a regular browser. It never really worked in chrome or safari but it wasn't a big deal to me as I just needed it in espresso.

thank you

[matthew-dean]

Since this is related to an earlier version (and likely to do with sync AJAX, maybe?) is this still an issue?

[seven-phases-max]

I guess it's safe to close either way (until someone reports the same with a current version :P).

[seven-phases-max]

Closing as no-longer-applicable.