SEA silently crashing when attempting to use .node DLL which works fine as a script

[mordof]

Version

v24.6.0

Platform

Microsoft Windows NT 10.0.26100.0 x64

Subsystem

No response

What steps will reproduce the bug?

I see it says without a github repository, but it would be challenging/lengthy to describe without as this involves needing a script setup using an available .node DLL, and bundling into a SEA application to demonstrate.

Hopefully it's ok to make an exception for this. I've made a github repo with a bare minimum example, a (hopefully clear) README to describe how to utilize it, and showcase how to test it running as a script, as well as testing the failing SEA app.

https://github.com/mordof/node_sea_crash_example

How often does it reproduce? Is there a required condition?

This happens every single time. The required condition is, as far as I can tell, simply trying to load a node-raylib .node DLL in when in a SEA app.

What is the expected behavior? Why is that the expected behavior?

The expected behavior is that running the SEA app will behave the same as running the identical script & dll as a javascript code file. This expected behavior is a successful raylib window example popping up.

What do you see instead?

The SEA app crashes silently without any error or output.

Additional information

No response

[joyeecheung]

addons are currently not supported AFAIK. @nodejs/single-executable - I think the last time it was discussed, the idea is that the file content needs to be bundled into the SEA, and then users will need to write them to disk at run time and use process.dlopen() to load them. Doc PR welcome if someone manages to get it to work.

[mordof]

@joyeecheung

Just to clarify, as I'm a bit confused: Are you saying that addons (even in the latter described pattern of using process.dlopen() to load them, are not supported currently?

[joyeecheung]

Sorry for being unclear - I meant that it is not supported out of the box/has no special machinery for support. But theoretically, putting them into the assets and then writing them to disk and then process.dlopen() should work (I've never tried).

[mordof]

Ah gotcha, thanks for clarifying. My example should behave the same way here, as far as I understand, as bundling into assets and writing them to disk: I can't think of a reason why writing them to disk at runtime would be any different from already having the file on the disk and using process.dlopen() to load them in.

The only reason I could think of for that to work is either a) if it being an asset modified the dll in some way to mark it was an asset, or b) if the temporary file written were known/recognized to the be asset somehow. I don't think either of these are the case (I could be wrong, but this is my current understanding).

If there are differences here, I'd be happy to learn about them and make adjustments to the example repo to make use of that so it's as close as desired.

All this to say that I'm like 80% sure that my example is in the state that would be best case scenario for it to have a chance of functioning.

[joyeecheung]

hmm right, in that case I am not sure why it isn't working. Maybe someone from @nodejs/single-executable would be interested in looking into this, though from the recent state of SEA, the chances of an volunteer looking into it would be low - you might have better luck trying to debug it with visual studio or windbg.

[ovflowd]

cc @RaisinTen