Segmentation fault when calling `chrome.privacy.services.autofillEnabled.set` about nw.js HOT 6 CLOSED

[5924:5924:0706/200655.791034:FATAL:nw_content_renderer_hooks.cc(53)] Failed to load node library (error: libatomic.so.1: cannot open shared object file: No such file or directory)

@skylarmt Do you have libatomic installed?

from nw.js.

@skylarmt Do you have libatomic installed?

Yes, at least on my dev machine, which had the same crash but with a less helpful stacktrace (unlike the VM, I think it's missing a utility that helps make useful bug report stack traces).

~$ sudo apt install libatomic1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libatomic1 is already the newest version (12.3.0-1ubuntu1~22.04).
libatomic1 set to manually installed.

Looks like it was missing from the VM though, and installing it there maybe helps?

from nw.js.

Another thing to note is this only seems to occur when an app hasn't successfully launched before. Deleting its data folder in ~/.config causes the bug again. I recall running into this crash on a laptop a few months ago, but assumed the laptop was just old and had some incompatibility, so I downgraded NW.js by a year or two and whatever version that was didn't crash.

from nw.js.

Note that autofillEnabled is marked as deprecated in the types: "since Chrome 70. Please use privacy.services.autofillAddressEnabled and privacy.services.autofillCreditCardEnabled."

from nw.js.

It shouldn't segfault though.

from nw.js.

Looks like it was missing from the VM though, and installing it there maybe helps?

@skylarmt After installing libatomic1 in the VM, does it still segfault? It doesn't for me.

from nw.js.