It's hard to know the cause without having more details.
As a troubleshooting step I would suggest running your application with just QEMU (no ESESC). That way you can verify that there are no bugs in the application code. It is possible that such a large matrix is causing a stack overflow in QEMU if you are allocating the matrix on the stack.
It's also possible that there is some other problem. But I would suggest verifying that the application works with standalone QEMU. If it does then you might want to run ESESC with gdb to try to get more details about the source of the problem.
-Gabriel