Chrome Version:53.0.2785.15 dev (64-bit)
Chrome OS Version:8530.13.0 (Official Build) dev-channel cyan
Chrome OS Platform: Acer R11
Network info: wifi 802.11ac

I have an android app that i want to get working with the new chromeOS android support. My (java android) app shells to a native binary (which is entirely statically compiled) using ProcessBuilder. The native binary is carried inside the android app as an asset.

This app and native binary work fine on all standard android devices, however in the chromeos build shown above, the pause() call seems not implemented or signals are ignored which causes the program to immediately exit instead of waiting for a SIGINT or SIGTERM. Putting print statements in the SIGINT and SIGTERM handlers show they are never called. However registring a signal handler calling signal and sigaction does NOT fail.

Expected Result: pause(2) works as specified in posix documentation

Actual Result: pause() does nothing and execution continues

How frequently does this problem reproduce? Always

What is the impact to the user, and is there a workaround? Android Native process cannot wait.