Screenshots and benchmarks are requesting more memory than you actually have on the camera.
So, as long as the error is handled nicely (without crash), don't worry about them. Look for crashes in normal usage (when you take photos, record videos, review them, browse menus and so on).
Screenshot is Canon code, so it's not aware of the memory backend. The only solutions are:
1) use shoot_malloc for everything (which is not exactly ideal, because when changing some stuff in Canon menu, they expect shoot_malloc to be 100% free)
2) rewrite the screenshot with ML code (described here, anyone would like to code it?
http://www.magiclantern.fm/forum/index.php?topic=10540 )