Live reload eats CPU

[danawoodman]

When I run live reload on my iOS app in the emulator (iPhone 5s simulation), the CPU jumps to about 170%. If I leave it open the simulator just freezes and I have to force quit it. Not sure if this is a know issue or if there is a way to work around it.

I'm on a 15" MacBook Pro Retina FWIW.

[sahrens]

Can you tell which processes are eating the most CPU?

On Mar 29, 2015, at 8:37 AM, Dana Woodman notifications@github.com wrote:

When I run live reload on my iOS app in the emulator (iPhone 5s simulation), the CPU jumps to about 170%. If I leave it open the simulator just freezes and I have to force quit it. Not sure if this is a know issue or if there is a way to work around it.

I'm on a 15" MacBook Pro Retina FWIW.

—
Reply to this email directly or view it on GitHub.

[jaygarcia]

I've never seen this, even when i've done hideous things like tax the OBJC JS bridge in a 10ms endless loop, querying for 512 floats ;).

Can you post code to replicate this?

FWIW, I am on a 2012 15" MBP Retina also.

[frantic]

Can you also include packager logs, your node version, etc.? Live reload uses long-polling and should not be causing this. Do you have watchman installed, watchman --version?

[jaygarcia]

I've still not had this issue :(.

[danawoodman]

Not able to reproduce, if I am, I'll reopen with details!

[jaygarcia]

@danawoodman Please close if this is no-longer a current issue. =)

[danawoodman]

Whoops, thought I did. Thanks!

[grabbou]

Still an issue here...

No livereload: CPU 1.0%
With livereload 10 seconds after: CPU 150%.

Havent even refreshed the code nor started interacting with the app.

The process is called este (the name of the app I am working on) and when killed, closes the debugging session in Xcode, so surely it's something related to this process.