NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Netgear Genie won't quit on Mac OS X
Unlike some people here, I had no trouble downbloading and installing Netgear Genie on my Mac system, first on an old iMac running OS X v10.6.8 and now on my new iMac running 10.11.2. Unfortunately the program's interface is terribly buggy. The worst problem is that once started, it refuses to Quit. I have to Force Quit it, which is not a good thing to have to do with any application. Other aspects of the interface suggest it's just an automated port of a program from some other operating system, or perhaps a Java app -- neither of which is a good thing.
It works alright when it's running (I guess) but I'm very disappointed in the quality of the app. It needs a good solid rewrite and upgrade, real soon now.
All:
Here's what (sorta) worked for me, based on escalation at Netgear to "Bianca" who seemed to really know how to troubleshoot. The fix that worked for me was to open the Genie package and to add a leading "1" to the component "libGeniePlugin_MyMedia.dylib", making it "1libGeniePlugin_MyMedia.dylib". This disables the Media Center features of the router, which I don't use anyway. Now, CPU usage is at about 10% (still too high for a "monitor", but tolerable), and I no longer have to force quit.Jonathan
23 Replies
Hi @RoboGenie,
Thank you for your feedback. Rest assured, we are always working on improving the features and user experience for the program.
Regards,
Dexter
Community Team
Having the same issue. Before purchasing the Nighthawk 7000 I'd read of the Netgear Genie problem, so I'm not too surprised to encounter it. But still disappointed.
This is an issue that Netgear has clearly known about for some time. The application does not take "quit" for an answer under OS X. El Capitán in my case.
I'm sure you can do better!
It is noted that you were working on the problem of having to force quit out of Network Genie as of last January, yet the problerm still persists. When is this issue going to be fixed?
All:
Here's what (sorta) worked for me, based on escalation at Netgear to "Bianca" who seemed to really know how to troubleshoot. The fix that worked for me was to open the Genie package and to add a leading "1" to the component "libGeniePlugin_MyMedia.dylib", making it "1libGeniePlugin_MyMedia.dylib". This disables the Media Center features of the router, which I don't use anyway. Now, CPU usage is at about 10% (still too high for a "monitor", but tolerable), and I no longer have to force quit.Jonathan
I'm experiencing the same thing on my late 2009 iMac running OS 10.11.2. Netscape Genie won't quit in the normal fashion. I have to force quit it every time.
On the plus side, I really like the graphical display of attached devices and the ability to add plain-English names. It's far more user-friendly than the list of attached devices in the router's configuration settings.
Jeff Frankel
Hi @jmfrankel,
Thank your feedback as well on this. This is noted and will certainly be looked at.
Regards,
Dexter
Community Team
I have the same problem, the app won't quit. Displays the "are you sure" message then the spinning ball of death goes forever. Only a force quit works. Has been this way for over 6 months now, both on older versions of mac os x and the newer El Capitan.
When will this be fixed?
I'm having the same issue here.
Have the same issue, running the latest Genie (Version 2.4.12) on MacBook Pro (13-inch, Mid 2012) with El Capitan 10.11.4 (15E65) - it just stuck on Quit. Have Netgear R8000 router if it helps.
Below is what reported in console log:
4/15/16 01:17:45.000 kernel[0]: process NETGEARGenie[2789] thread 128206 caught burning CPU! It used more than 50% CPU (Actual recent usage: 71%) over 180 seconds. thread lifetime cpu usage 90.091226 seconds, (86.067295 user, 4.023931 system) ledger info: balance: 90002656539 credit: 90002656539 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 125908595734
4/15/16 01:17:45.818 ReportCrash[3954]: Invoking spindump for pid=2789 thread=128206 percent_cpu=71 duration=127 because of excessive cpu utilization
4/15/16 01:17:46.800 spindump[378]: Saved cpu_resource.diag report for NETGEARGenie version ??? (???) to /Library/Logs/DiagnosticReports/NETGEARGenie_2016-04-15-011746_XXXXXX.cpu_resource.diag
4/15/16 01:28:32.055 spindump[378]: Saved hang report for NETGEARGenie version ??? (???) to /Library/Logs/DiagnosticReports/NETGEARGenie_2016-04-15-012832_XXXXXX.hang
Thank you! This workaround should be at the top of the comments. Had I not went to the next page i wouldn't have found it.
