This is totally awesome and hopefully "mainstream debuggers" will learn from this.
Here's another example how memory visualization is useful, this time in an 8-bit home computer emulator (where such things are very trivial to do in realtime, because the performance difference between an 80's home computer and a modern machine is so big).
You can see how a visual effect in a scene demo works by looking at the memory access "heat map":
I also found the "execution heatmap" very useful for debugging, this just "paints the map" where the instruction pointer is reading memory, with the current location extra highlighted. One can understand a lot of things about a given program by just watching execution jump around in memory (such as, where are the "hot loops" versus what is one-time code, what memory regions are code, and what are data, etc...
Here's another example how memory visualization is useful, this time in an 8-bit home computer emulator (where such things are very trivial to do in realtime, because the performance difference between an 80's home computer and a modern machine is so big).
You can see how a visual effect in a scene demo works by looking at the memory access "heat map":
https://twitter.com/FlohOfWoe/status/1075083521193062401
I also found the "execution heatmap" very useful for debugging, this just "paints the map" where the instruction pointer is reading memory, with the current location extra highlighted. One can understand a lot of things about a given program by just watching execution jump around in memory (such as, where are the "hot loops" versus what is one-time code, what memory regions are code, and what are data, etc...
(edit: replaced the link with a better example)