61–70 of 241 posts
I always wondered why people bother with htop on OS X when the built-in Activity Monitor.app is so nice already. I only use htop on remote boxes myself.
1. By creating and closing process very rapidly, one could easily reproduce this problem. I used something like `while true; do sh -c "exit 0"; done`. The entire OS dying to rapidly spawned/exited processes permits a pretty nasty DoS. Good thing that nobody ever uses macs as servers or shared machines.
High Sierra seems like a great OS if you want an unstable workstation that doesn't work with tools you've used everyday for well over a decade.
It’s weird, I keep hearing things like this but have encountered literally no issues with it on my mid-2015 MacBook Pro... Is there some particular hardware that it’s dodgy on or am I just lucky?
I feel like my 2014 rMBP is silently yelping "What have you done to me?" every day.
I would switch but to what? Windows/Linux are just as user hostile.
On Mac OS 10.4 (tiger) when I left Activity Monitor going in the background for a few minutes and returned to it, sometimes it would all of a sudden refresh the values super super fast with historical data (appearing to catch up on the iterations that it did not display.) On 10.6, when I ran Windows in a virtual machine while it was doing windows update, and left it running in the background for a few minutes and ret…
High Sierra seems like a great OS if you want an unstable workstation that doesn't work with tools you've used everyday for well over a decade.
I came for the filesystem bugs, I stayed for the absurd root exploit, but its the little crashes, rendering glitches, and feeling of general instability that made me fall in love with High Sierra...
Earlier quoted context omitted.
I'm on macOS High Sierra for the spontaneity. Every morning, I go to wake my Macbook Pro with two 4K USB-C connected displays and external keyboard and mouse. Will one display turn on? Both? Neither? Who knows!
Store the screen layout using serials from the EDIDs. Why it doesn’t do this and “tries” to guess their position somehow is beyond me. I use the OWC TB3 dock with dual Asus PA328qs with the latest firmware. Because of apparently some lame design decisions, in order to run dual external monitors over a single TB3 port, you need the dock, which has one DisplayPort output, then a TB3-> DisplayPort (via USB-C alt mode II…
What does this mean/how do you do it?
1. By creating and closing process very rapidly, one could easily reproduce this problem. I used something like `while true; do sh -c "exit 0"; done`. The entire OS dying to rapidly spawned/exited processes permits a pretty nasty DoS. Good thing that nobody ever uses macs as servers or shared machines.
Geez; does this mean it could do the same when compiling a large codebase with Make?
(I suspect that recursive makes do enough compute in between invocations to slow down and avoid this bug. If the OS was dying in everyday compile jobs it'd be much bigger news.)
EDIT: I think that I might've misread this - it might be that spawning processes pushes htop through codepaths that can cause the bug. So it's more like "a malicious app could kill your system the instant you open htop". In which case, yes, a recursive make while you have htop would would do it. Rather less significant.
I've had a similair problem with Transmission for years. Doing more then a few transfers locks up transmission and then the entire machine. Issuing a halt at the terminal sometimes will reboot the machine, but moist of the time it just hangs. I would switch but to what? Windows/Linux are just as user hostile.