Linked by Thom Holwerda on Mon 26th Feb 2018 18:13 UTC

Flaky failures are the worst. In this particular investigation, which spanned twenty months, we suspected hardware failure, compiler bugs, linker bugs, and other possibilities. Jumping too quickly to blaming hardware or build tools is a classic mistake, but in this case the mistake was that we weren’t thinking big enough. Yes, there was a linker bug, but we were also lucky enough to have hit a Windows kernel bug which is triggered by linkers!

Thread beginning with comment 654196
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: NT is still garbage
by evil on Wed 28th Feb 2018 10:40 UTC in reply to "RE[4]: NT is still garbage"
Member since:

I used it more than 10yrs ago to avoid system locks, while some process leaks memory extensively.

New approach is cgroups.

And LXC is another beast, meant for lightweight virtualization.

Reply Parent Score: 2

RE[6]: NT is still garbage
by avgalen on Wed 28th Feb 2018 16:35 in reply to "RE[5]: NT is still garbage"
avgalen Member since:

Interesting links! It doesn't seem like any of that would prevent the mentioned issue by default though.

The main problem is always that you want all resources to be available to every program...but you don't want 1 program to take up resources that another program needs.

So you end up configuring a generic system for a specific workload
or you end up with a system where 1 program can limit the performance of the 2nd program
or you end up with a system where a program runs non optimal

Reply Parent Score: 3