Terminal lockup/freeze during a haikuporter build of mailnews

[cocobean]

Terminal lockup/freeze during a specific haikuporter build of mailnews 2.0.0.25-2 on Haiku R1B4 hrev56949+2 x64 (nightly build). Does not happen on haikuporter build of mailnews using Haiku R1B4 x64 (hrev56578+69 and hrev56578+77) stable release updates.

NOTE: Does not affect desktop itself - just the active terminal. Closing terminal and restarting build within another terminal gave same result. Requires 'shutdown -r' for build to complete successfully.

Ref: ​https://github.com/haikuports/haikuports/issues/8487

[waddlesplash]

Can Terminal, or the HaikuPorter instance, be killed with kill -9 or Vulcan Death Grip?

[cocobean]

Yes. I can close/exit the terminal using the terminal GUI or 'kill application/thread' methods. Can't 'kill job' (i.e. CTRL-C / CTRL-Z) through the 'hung' terminal window itself.

[waddlesplash]

Being unable to kill jobs via CTRL+C is not necessarily indicative of a bug in Terminal, it may indicate the application has intercepted the signal in question.

If you can kill the application with "kill -9" and all returns to normal, this isn't a Terminal bug.

[cocobean]

I thought this was the case when I killed the terminal window. But, if I rerun the same job in another terminal window - it will hang the build process in the new terminal window (same build point). I can only successfully complete the build job if I reboot the machine.

Other haikuporter builds are successful on same machine. I can wait until Haiku R1B5 for retesting.

[waddlesplash]

If the Terminal can be closed/exited via the GUI or by killing the application, then this isn't a Terminal bug.