Are you sure about the 'ABRT' signal — it's a rather unusual signal to send, as - at least on Unix (not sure about its Windows emulation) - it would abnormally terminate the process, with the default action leading to a core dump (unless disabled), just like SIGSEGV, SIGILL or SIGFPE.

Also, how exactly does it "crash"? Immediately upon start, when you interrupt it, etc... (maybe you're just seeing the result of you yourself aborting the subprocess?)