Segmentation fault in RHEL containers

[gabrielcradden]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Affected package

remark-cli@12.0.1 with remark-validate-links@13.1.0 (but appears to affect versions 11+ of remark-cli

Steps to reproduce

On some RHEL9-based containers, remark --use validate-links hits a segfault no matter the input files.

This happens with the latest node, remark, and remark-validate-links versions. However, I don't see it on my WSL which is also using redhat, or on the node:24-alpine container.

Annoyingly, I couldn't reproduce this on the UBI 9 base container but only on one of our internal build containers, so I can't give you good repro steps.

Actual behavior

Segmentation fault (core dumped)

I couldn't get anything out of the core dump file. I've attached the last few hundred lines of strace for the command.

remark strace.txt

Expected behavior

Not segfault

Runtime

v24.4.1

Package manager

npm 11.4.2

Operating system

Red Hat Enterprise Linux 9.6 container image

Build and bundle tools

No response

[wooorm]

This seems more a problem for them, then?

[ChristianMurphy]

Agreed with @wooorm
This sounds like a much lower level bug with node on RHEL.
Given it is RedHat Entireprise Linux, opening a ticket for support is likely already covered by your support contract with RedHat.

[gabrielcradden]

Thanks - yes I think you are right - just saw we started hitting this bug after switching to a RHEL-based container.

Will raise with RedHat.

If I get a response from RedHat, I'll try and remember to update this ticket in case someone hits this in future.

[github-actions]

Hi! This was closed. Team: If this was fixed, please add phase/solved. Otherwise, please add one of the no/* labels.

[github-actions]

Hi team! Could you describe why this has been marked as external?

Thanks,
— bb