Mac client needs work
Posted: Sun Mar 08, 2020 1:15 pm
Could I begin in saying, I think the work here is ground breaking & I welcome being part of it.
I installed the standard Mac client a few days back, with a generic install.
1) I found generally system instability issues began (MacBook Pro, Retina 15 inch, 2.8 Ghz Quad core i7, mid 2015, OSX 10.15.3).
I had several hard crash/reboots within a few days and I was forced to stop running the tool;
2) What I then found, was the tool was still spawning in the background on re-boot, even though I had not started the app;
3) Even killing the tool (sudo killall -9 FahCore_a7), I noticed it re-spawned within seconds;
4) Finally, I had to remove by: directory hand tree /Library/Application Support/FAHClient & binary /usr/local/bin/FAHCoreWrapper ;
I found this overly aggressive behaviour, almost virus like. I need the ability to say when the app runs, I have commercial deadlines and at times need all the cycles I can get.
When I am not running the app, I don't expect the tool to be running. I never authorised any system level (owned by root) background jobs, especially ones that self-regenerate.
Could I suggest an immediate review of the OS X client. I'm happy to be a tester when you feel the above are addressed.
I would give serious consideration to suspending the OS X downloads.
I installed the standard Mac client a few days back, with a generic install.
1) I found generally system instability issues began (MacBook Pro, Retina 15 inch, 2.8 Ghz Quad core i7, mid 2015, OSX 10.15.3).
I had several hard crash/reboots within a few days and I was forced to stop running the tool;
2) What I then found, was the tool was still spawning in the background on re-boot, even though I had not started the app;
3) Even killing the tool (sudo killall -9 FahCore_a7), I noticed it re-spawned within seconds;
4) Finally, I had to remove by: directory hand tree /Library/Application Support/FAHClient & binary /usr/local/bin/FAHCoreWrapper ;
I found this overly aggressive behaviour, almost virus like. I need the ability to say when the app runs, I have commercial deadlines and at times need all the cycles I can get.
When I am not running the app, I don't expect the tool to be running. I never authorised any system level (owned by root) background jobs, especially ones that self-regenerate.
Could I suggest an immediate review of the OS X client. I'm happy to be a tester when you feel the above are addressed.
I would give serious consideration to suspending the OS X downloads.