Bug 43655

GemStone/S 64 Bit

3.4.2, 3.4.1, 3.4, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1, 3.0.1, 3.0, 2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.7, 2.4.4.6, 2.4.4.5, 2.4.4.4, 2.4.4.3, 2.4.4.2, 2.4.4.1, 2.4.4, 2.4.x, 2.4, 2.3.1.6, 2.3.x

All Platforms

Use of SIGUSR1 can hang gem/topaz process

When sending a SIGUSR1 signal to a gem or linked topaz process to generate a stack trace, there is a rare possibility of hanging the process, due to a deadlock between malloc / free operations during the handling of the signal.

The gem/topaz process can only be terminated using "kill -9".  Attempts to use stopSession: will only cause the OOB thread on the process to also deadlock on a malloc operation.

Workaround

No workaround.  Use "kill -9" to terminate the process.


Last updated: 10/19/15