I am hitting some cases where /proc/self/maps does not fit into 64MB.
256MB is lots of memory, but it's not radically more than the current 64MB.
Ideally we should read/parse these huge files incrementally,
but that's lots of work for a debugging/introspection interface.
So for now just bump the limit.
Depends on D112793.
Is 64MB more likely to be exceeded on 64-bit systems?
If so, maybe make the size conditional on bit-ness of the system? Because 64 vs 256 MB might be a lot for some 32-bit system.