upvote
Guarding against that seems like a bad idea, but even then just use a couple less threads than physical cores. Don't get too clever.

You in particular should probably disable a couple cores until your hardware stops being defective. Have you looked into updates and voltage droop compensation settings?

reply
That sounds like a faulty motherboard. Return it.
reply
Users don't care that it's a problem with the motherboard. They have a working computer, they buy a game and it doesn't work, they blame and return the game.

Users can be unreasonable, but in this case I agree - if I reported an issue to a vendor and their response was "return your motherboard" I wouldn't work with that vendor again.

reply
We can't form the world around literal bad hardware. That's completely insane. The world would fall apart.

> I wouldn't work with that vendor again.

Possibly rightly so, if it's bad motherboard hardware. Could also be a bad power supply, bad ram, bad CPU, user misconfiguration, etc. It's a complex system, where everything has to NOT be bad for it to be deterministic.

There's a necessary level of competence required with self built systems, or any other task in human life that you're not paying someone else to do for you. That's fine. Go buy a MacBook or a pre built system if that threshold of competence can't be met. That's why they exist, for people that can't or don't want to bother.

reply
Haha, that really depends. If you look at it from the viewpoint of a failsafe, like brakes in lifts that activate without central control, backup parachutes, etc. Then it makes some sense for resource intensive software to guard against weird edge cases like this. It's just that they measured the wrong thing.
reply
Those have nothing to do with the required assumption of determinism in the hardware that software must enjoy.

You're examples are flawed. Those are to safely halt operation on failure. What you're suggesting with the software is to limp along pretending everything is ok.

The proper test, more in line with your others, would be to catch failure and halt operation. Since, in your case c the human isn't competent enough for that, it would maybe be a self test initiated by the operating system, then a refusal to continue when the hardware problem is identified, emulating all the periodic inspections that are part of all the proper operation of all the physical systems your mentioned.

reply
We don't use elevator brakes or backup parachutes as an excuse to let the primary fail under normal load. Those are for emergencies.

I think the elevator analogy to this bug is that the elevator goes too fast and triggers the brakes if you input target floors more than 8 apart. You don't fix that by having the user or user software be more careful about button placement, you fix the hardware/firmware.

reply
Sounds like they don't have a working computer. Computer users occasionally do things that end up pegging all cores, so I'm pretty sure that someone in that case would know their computer has some kind of issue.
reply
Why aren't you storing all your variables with reed solomon encoding in case you have a user with bad ram?
reply
That seems like a you problem - undervolt your cpu.
reply
It’s just reality that motherboards can malfunction or degrade in peculiar ways that a manufacturer’s quick boot up checks cant always catch. No matter the reliability claims.

If they want to cater to customers who foolishly reject reality and take every claim from manufacturer’s at face value… then foolishly misaimed blaming seems expected?

But if they just roll over and swallow the foolish blaming without even challenging customers to double check, then they are also facilitating more nonsense.

reply