Talk:Memory corruption

I think this article needs significant revision. Presently, the article is very C/C++-centric. Memory corruption can come from sources other than programming errors. It can come from "soft" sources other than programming errors. For example, a misbehaving superuser can easily trigger memory corruption if he so desires. It can also come from "hard" sources such as hardware defects or external interference. AaronWL 04:55, 5 November 2006 (UTC)

Same as Data corruption?
This page is very similar to Data corruption, I believe it should be either merged into or just be a redirect. Mooskagh (talk) 13:41, 29 November 2020 (UTC)


 * Memory Corruption is a very different concept than things like bit-rot or bit-flips. Adinsx3 (talk) 09:42, 24 June 2022 (UTC)

Memory leaks are memory corruption?
Memory leak is not necessarily an effect of bad memory management logic in a given programming platform. Memory leak can happen e.g. because user code is missing the code that release the memory - in such scenario there is no situtation where a code accesses memory it shouldn't access and there is no error in non user code specific memory management logic.

Memory leaks do not correspond to the description in the beginning of this article, i.e.: "Memory corruption occurs in a computer program when the contents of a memory location are modified due to programmatic behavior that exceeds the intention of the original programmer or program/language constructs; this is termed as violation of memory safety."

Memory leaks do not violate memory safety. They are just wasteful and could lead to denial-of-service, crashes or instabilities due to resource exhaustion, but that's a different story. 37.47.65.56 (talk) 14:59, 14 July 2024 (UTC)