> How big a problem was this in practice? It can deadlock and cause crashes if you do use a library impacted. It's sometimes hard to tell and you'd have to dig

> How big a problem was this in practice? It can deadlock and cause crashes if you do use a library impacted. It's sometimes hard to tell and you'd have to dig into the source. Sometimes the library maintainer wouldn't update the code to a different method for <reasons>. > Is this really common? Yes, maybe not in obvious ways e.g. many developers use Spring, which is backed by a large organization and you'd assume to have things covered but under the hood Spring itself uses many libraries and some often open source without much support (can be a personal project by a single developer).