Uncaught signal: 11 Segmentation fault when using the lib about jsonld-signatures

[davidlehn]

• What version of jsonld-signatures and Node.js?
• Just to check, you're saying that installing jsonld-signatures in addition to all those packages causes problems?
• Does this happen even if you don't call anything in jsonld-signatures? Is it just while starting up?
• If you are calling something, what is it?
• Can you narrow it down to a simple test case project you could share?
• Causing segfaults is not a common thing in Node.js. However, the one thing we have found that will almost certainly cause non-deterministic segfaults is mixing native ESM use with the esm.js package. It's terrible.
• I'd check npm explain esm to see if you are using the esm package anywhere. If you are, that's a very likely cause. The solution is to tear out esm from everything, or ensure you are not also using native ESM code. This can be a difficult ask, but esm is unmaintained and obsolete so it needs to be removed at some point.
• You'll notice jsonld-signatures is just ComonJS, not ESM, but that doesn't stop this bug from happening for reasons I don't understand. It's a very odd bug that be triggered in odd ways, and it may be that some module loading pattern jsonld-signatures uses triggers the problem.
• If you're not using esm.js, then it's difficult to help without more details or, ideally, test code to run. You could run node in gdb to try and catch the stack traces. That's how I find these esm.js issues. It'll crash in some import or require stack.

[dlongley]

Closing as not an issue with this library.