DLL that was not present in memory despite not being formally unloaded
devblogs.microsoft.com
DLL that was not present in memory despite not being formally unloaded
1–10 of 49 posts
Re: DLL that was not present in memory despite not being formally unloaded
#2That's some doggedly determined back tracing to uncover an unexpected heisenbug (loose meaning).
So a total of 46% of the crashes were due to this rogue force-unload of a DLL. This is a case of bucket spray, where a single underlying cause generates a large number of different types of crashes.Re: DLL that was not present in memory despite not being formally unloaded
#3> The good news for the shell32 team is that they are off the hook; they are the victim. The bad news is that we don’t know who the culprit is.
The story of software development through the ages.
Re: DLL that was not present in memory despite not being formally unloaded
#4That's some doggedly determined back tracing to uncover an unexpected heisenbug (loose meaning). So a total of 46% of the crashes were due to this rogue force-unload of a DLL. This is a case of bucket spray, where a single underlying cause generates a large number of different types of crashes.
We've not yet seen sufficient evidence this is any type of heisenbug.
Re: DLL that was not present in memory despite not being formally unloaded
#5Re: DLL that was not present in memory despite not being formally unloaded
#6I see posts like this, this deep dive into the call stacks and am always humbled and reminded of the limits of my knowledge about computers and programs.
Re: DLL that was not present in memory despite not being formally unloaded
#7I see posts like this, this deep dive into the call stacks and am always humbled and reminded of the limits of my knowledge about computers and programs.
Not a programmer?
Re: DLL that was not present in memory despite not being formally unloaded
#8Part two: https://devblogs.microsoft.com/oldnewthing/20260626-00/?p=11...
Part 1 was interesting; it isn't clear why he split that into a Part 2 since it adds little to the story and is a paragraph long.
Re: DLL that was not present in memory despite not being formally unloaded
#9> The good news for the shell32 team is that they are off the hook; they are the victim. The bad news is that we don’t know who the culprit is. The story of software development through the ages.
When you’ve eliminated all possible explanation, it’s time to pack it in.
Re: DLL that was not present in memory despite not being formally unloaded
#10I see posts like this, this deep dive into the call stacks and am always humbled and reminded of the limits of my knowledge about computers and programs.
Goes both ways, author probably knows little about FPGA programming, React or PyTorch.