If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...

If you have a not-so-usual solution for your problems but need to justify it to your boss...

If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...

...then 'No Bugs' Hare on Soft.ware might be the right place for you.

Your mileage may vary. Batteries not included

Assorted Rants Tagged ‘Memory Management’, page 1:

Java vs C++: Trading UB for Semantic Memory Leaks (Same Problem, Different Punishment for Failure)

posted October 30, 2018 by "No Bugs" Hare

Quote:	“with all due disrespect to mutable static/global data, I have to say that the problem of semantic memory leaks is NOT restricted to statics”
Another Quote:	“semantics of good code is about the same regardless of Java/C++ choice”
	[→]

posted July 4, 2018 by "No Bugs" Hare

Quote:	“if you DO want to get performance from changing mallocs, make sure to test them with your own app”
Another Quote:	“in our humble opinion, overall winner so far (by a nose) is jemalloc.”
	[→]

posted June 21, 2018 by "No Bugs" Hare

Quote:	“We won’t ever get (almost) any virtual memory back, plain and simple”
Another Quote:	“relocation allows not only to reduce fragmentation, but to eliminate it entirely.”
	[→]

posted May 1, 2018 by "No Bugs" Hare

Quote:	“Allocator-based serialization for (Re)Actors is extremely fast (for x64 – around tens of ms per 100MB of state)”
Another Quote:	“Per-(Re)Actor allocators can be implemented without any changes within (Re)Actor itself (i.e. all the necessary changes can be confined to Infrastructure Code).”
	[→]

posted March 14, 2018 by "No Bugs" Hare

Quote:	“we DID get a perfectly usable C++ dialect which is also 100% safe against memory corruption and against memory leaks.”
Another Quote:	“we can (and often SHOULD) have different approaches to safety of the Reactor::react() and the rest of the code.”
	[→]

posted August 15, 2017 by "No Bugs" Hare

Quote:	“‘Safe with relocation’ mode will allow us to eliminate dreaded ‘external fragmentation’ – which tends to cause quite a bit of trouble for long-running systems”
Another Quote:	“For a long while, I have been a strong proponent of message-passing mechanisms over mutex-based thread sync for concurrency purposes”
	[→]

posted May 1, 2014 by "No Bugs" Hare

Abstract:	Sometimes it makes perfect sense to use 32-bit application on 64-bit platform.
Quote:	“It is obvious that for N between 13,000,000 and 21,000,000, 64-bit application works about 1000x slower.”
	[→]