Re: [R] Fwd: Help: malloc/free deadlock in unsafe signal handler 'Rf_onsigusr1'

Thanks luke. cc hawq dev team. I sent this email to R-devel 2 days before forwarding it to R-help, but no one reply. Is there any workaround? When were SIGUSR1 and SIGUSR2 sent in R? Or maybe we should move all operations not too emergency out of signal handler? Thanks. On Tue, Aug 2, 2016 at

Re: [R] Fwd: Help: malloc/free deadlock in unsafe signal handler 'Rf_onsigusr1'

The handlers for SIGUSR1 and SIGUSR2 are really intended as an emergency break, not for ordinary programming. These could be rewritten to be safer but that would make them less immediate. Followups would be more appropriate on R-devel. Best, luke On Mon, 1 Aug 2016, Ming Li wrote: Hi all, I

[R] Fwd: Help: malloc/free deadlock in unsafe signal handler 'Rf_onsigusr1'

Hi all, I am working on a bug, which running PLR on HAWQ. The process hung and can't be terminated. >From my investigation, it seems signal handler 'Rf_onsigusr1' trigger a malloc/free deadlock. The calling stack is below. Thread 1 (Thread 0x7f4c93af48e0 (LWP 431263)): #0 0x7f4c9015805e i