Comment 12 for bug 1452005

Is it an issue of different instances? It looks like as if the call stack is still valid after SIGBUS.

One idea is to guard all accesses to the mapped mamory, by a wrapper class.
In the signal handler we may check if we are in the guarded region.
If yes. stop decoding the file in the current context and clean up.
This finally may look like a try catch region.

But never mind, probably it is not possible because I have not found an example on the web. :-/