> Also, if there is some way of viewing the libc function name instead of > address, that would be helpful.
I am sure these are malloc, free, memset, memcpy, etc. As the size increases they contribute more and more. Still, dense_raster_render must be spending some time just walking around the huge matrix. If you press Enter and Annotate, you will see the hottest lines.
