-
Notifications
You must be signed in to change notification settings - Fork 339
Closed
Description
To reproduce, in RStudio:
- Use Cmd + Shift + T to run tests,
- Wait until the parallel test runner has started,
- Stop the running tests with the stop button.
The running R process receives a SIGTERM and exits, but the sub-processes are left behind.
At least on macOS, those processes get stuck in an infinite busy loop, chewing up lots of CPU. lldb reports:
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x7)
* frame #0: 0x00000001026a74fc libR.dylib`R_GetTracebackOnly(skip=0) at errors.c:1564:19 [opt]
frame #1: 0x00000001026a76a4 libR.dylib`R_GetTraceback(skip=<unavailable>) at errors.c:1605:9 [opt]
frame #2: 0x0000000102701720 libR.dylib`sigactionSegv(signum=11, ip=0x00000001284a8250, context=<unavailable>) at main.c:602:2 [opt]
frame #3: 0x0000000186206a24 libsystem_platform.dylib`_sigtramp + 56
so it seems like the R processes are getting stuck recursively handling SIGSEGV errors.
Metadata
Metadata
Assignees
Labels
No labels