On Thu, 2024-12-12 at 13:23 -0500, Greg Wooledge wrote: > On Thu, Dec 12, 2024 at 13:20:28 -0500, Roy J. Tellason, Sr. wrote: > > On Wednesday 11 December 2024 06:00:37 pm Greg Wooledge wrote: > > > This makes memory leaks less common, but when they *do* occur, > > > they're > > > quite difficult to find. Usually it means you've accidentally > > > retained > > > a reference to the object in question in some part of the program > > > that > > > never goes away. > > > > I'd really love it if firefox didn't consume increasing amounts of > > memory as time went on... > > > > Why would it do that? That's been the case for a long time over > > many versions. > > Because finding and fixing memory leaks is *really difficult*. And > not > much fun. And doesn't let you put fancy new blurbs on your "what's > new" > page.
Some languages have dynamic-memory facilities that inherently do not leak, unless you are intentionally careless. But C and C++ are not in that set.
