I was looking through my Registry, and searching for Scrivener (to find a particular registry entry), and came upon




0x1d5203830ac8a8f (132047189784169103)[/code]

Which according to https://www.epochconverter.com/ldap is about 9:30 am on Jun 11, 2019.

And I have no idea what I did 20 days ago to cause that. But a “heap leak” might mean something to the devs. Unfortunately, while Windows RADAR detects them, it doesn’t tell us what was happening then (or, at least, not without more trouble than I want to go through right now).

Hi. I think heaps are just specific containers of Windows memory. I don’t know if this is still valid (I’m thinking of Windows 3.0 era), but there were User Heaps and GDI heaps. User heaps contained information about applications, and were supposed to be released when the app closes. If it didn’t release the memory completely, I believe they classified it as a leak.

Full heaps used to be a problem, requiring you to restart your computer, especially if you opened and closed the same app a lot. I haven’t heard the term used in a while, but maybe Windows still uses this architecture.