7 ms·
> It seems that memory bugs carry a higher risk of being completely invisible except in deliberately contrived situations. Do they really carry a higher risk o
by _gabe_ 2y ago
> It seems that memory bugs carry a higher risk of being completely invisible except in deliberately contrived situations.
Do they really carry a higher risk of being invisible though? You don’t need to “contrive” situations either. My company just spent 6+ months trying to solve a JavaScript undefined symbol bug stemming from a library. When we finally tracked it down, it was because we were using import instead of require, which the documentation didn’t clarify was important. The fix we implemented was nowhere near where we expected the bug, and the only reason we finally solved it was because we had exhausted all other options. Sounds the same, if not worse, as a difficult to track memory bug to me.
- n4r9 2y agoI'm not sure if I get your point here, but it's possible that "invisible" was too ambiguous. What I meant was that a memory bug may be less likely to cause noticeable functional changes to the behaviour of the program during everyday usage. I.e. the client won't notice them.