Firefox Heap CorruptionMay 21, 2008 – 6:08 AM
When executing the example below, it tries to load the applet, runs into memory and fails to close. In my test environment the browser becomes unresponsive and text being typed in the url-bar is reversed. If I let it run a couple of minutes, or try to navigate it results into a heap corruption, for God knows what. Anyway, I am too lazy to perform a stack trace, I’ll leave that as an exercise for you, and also because my current copy of AutoDebug has expired 🙂 Heap corruptions are usually very serious but hard to exploit correctly, because if controlled properly it can be used to execute code on a users system. I won’t go into that because I simply don’t have the time, concentration nor interest for it. So bear with me on this one, I might do an article on this in the near future.