Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Interesting concept, however from the wireshark analysis it seems like the packets are identical in sequence, up until the part where it stops working of course... also, the most important bit which I'll edit in my question - I don't need to run Procmon each time for the application to work - if I reboot the workstations everything still works! Seems like a one time modification...
    – lcam
    Commented Aug 22, 2017 at 11:45
  • I acknowledge the dead look is a remote possibility. But still it's feasible. The order or the packets is not critical for producing the dead lock, but the timing. If SW2 replies very quickly and SW1 is not well designed, it maybe missed up the packet and gets stacked waiting for it. It's like getting just on time to the bus stop, but nobody is waiting. You don't know if the bus is to come, or if it's gone. Check the timing of the packets from the different servers, or try running any software -other than Procmon- which creates a heavy load on the server to see if you get the same effect. Commented Aug 22, 2017 at 12:20
  • Thanks for the explanation piedramania - I am now looking into replicating the problem on an offline workstation so I could experiment on the issue. I'll give it a go. Thanks!
    – lcam
    Commented Aug 22, 2017 at 12:23
  • This explanation does not hold if everything now works and keeps on working without Process Monitor.
    – harrymc
    Commented Aug 22, 2017 at 12:24