Mac 10.10 (Yosemite): Brackets Helper process erroneously shown as "Not Responding" in Activity Monitor

[dalcala]

Description:
Mac 10.9: Brackets Helper process Not Responding 15-20 seconds after launch in Activity Monitor. Shows up in red text in Activity Monitor. The same thing happens with Google Chrome on Mac 10.9, so this is a tracking bug. According to Peter Flynn, it's the GPU helper. We checked the Chrome process ID that was not responding > opened Chrome's task manager (hamburger icon > Tools > Task Manager) > mapped not responding process ID from Activity Monitor to process ID in Chrome Task Manager > GPU Process. Here is the Chromium bug for this issue:

Issue 304860: Mavericks: Helper processes shown in Activity Monitor as "Not Responding"
https://code.google.com/p/chromium/issues/detail?id=304860

Repro on Mac 10.9 using Brackets Sprint 33 10188 GM, Sprint 32 9791 GM, Sprint 31 9569 GM. UTR on Mac 10.8 using BK Sprint 33 GM 10188.

Repro steps:

1. Install Brackets on Mac 10.9.
2. Launch Activity Monitor.
3. Launch Brackets.
4. Watch Activity Monitor for ~15-20 seconds.

Actual results:
Activity Monitor says Brackets Helper process is not responding.

Expected results:
Brackets Helper is responding.

Workaround:
None. Everything seems to be working fine, so it appears this is a false positive. Comment from Chromium bug: "This is an issue with how Activity Monitor determines responsiveness – these processes are running perfectly fine. (We changed chrome to work around that Activity Monitor issue, and the fix will reach you eventually, depending on which channel you use, how far we merge this, etc.)"

[peterflynn]

Changed title to clarify that process isn't actually unresponsive (was: "Mac 10.9: Brackets Helper process Not Responding 15-20 seconds after launch")

[pthiess]

@JeffryBooher tagged as native shell

[JeffryBooher]

Do we know which version of Chrome this was fixed?

[njx]

I don't entirely know how to read Chromium bug tracker stuff, but from the auto-generated messages at the bottom of the comment thread in the bug that @dalcala mentioned, it looks like the fix was merged into the 1650 branch.

[ElegantScripting]

I know this is relatively old, but from what I can see on my Mac, this isn't related to chrome. I don't use Chrome, only Safari.

Brackets Helper on my Mac isn't responding as well, on fresh restart, without the use of live preview.

[prksingh]

This bug is about brackets helper 'erroneously' appearing unresponsive in Activity monitor.
The application should not be affected by this. Do you mean the same?

Also which version of brackets are you using? I notice from the comments above that the issue may have been fixed in the chromium build we integrated some time back. Are you seeing this in Brackets 1.2?

[peterflynn]

@prksingh Good catch! It does appear fixed now on Mac, so let's close it.

@ElegantScripting If you're seeing slow performance when using Live Preview, that's a different issue. Could you file a new bug with more details? (E.g. does it happen with the simple Getting Started project that comes with Brackets too, or only with your own projects?)

[ElegantScripting]

• No live preview
• Extensions disabled
• Restarted brackets
• Using latest version

[peterflynn]

Hmm, so apparently looks like the Chrome bug regressed on Yosemite: https://code.google.com/p/chromium/issues/detail?id=397642.

They did land a fix on the Chrome 39 2171 branch shortly before we started out upgrade to CEF 2171, but I'm guessing we just narrowly missed the boat on picking up that fix. (If I'm reading the version numbers right, we need 2171.50 and we currently have 2171.36).

Updating the bug title and reopening.

[schroef]

Im seeing this on OSX 10.10.2 its a old mac and ive got latest bracket 1.11
What i find weird is that in post, while its was 2 yr ago, he talk abouts brackets 1.2???

Reloading without extension still shows the issue. Beeing that my system is old it doesnt really slow down unless i open a couple documents and do some other heavy stuff. Its a core 2 duo 2.4 with 4g Ram.

I never really bothered about this cause normally i work on a macbook pro 16g mid 2015.