Emerging dev-util/electron-1.3.13-r1 succeeds without errors, however attempting to use the /usr/lib/electron-1.3/node binary results in a segmentation fault. I have stepped through the ebuild process manually, and the binary in question has no issues when being run from inside the image directory; it is only after it is merged to the live system that issues arise. A similar thing seems to be happening on other versions of electron too. System Info: https://drive.google.com/open?id=0B2yhQ3O4tL3kNkgxdGFjRzJtY0U Build Log: https://drive.google.com/open?id=0B2yhQ3O4tL3kQmJWdTVabmY0NFk Files:
Please attach the two files (compressed, if large). The developers use tools which rely on attachments and we do not want to depend on third party servers.
Created attachment 474210 [details] Build Log (xz archive)
Created attachment 474212 [details] System Info
Apologies for that, I hadn't used the attachment feature before. I also have an archive of the working directory if it's needed, although it's too big to upload as an attachment.
As a side note, I wouldn't be surprised if there were issues with other files in the package too; I am unable to run any electron based app, even pre-compiled ones (e.g. AppImages). So far I've tested Hyper, Gitkraken, Discord, and Atom without success.
Have you tried a newer GCC version? Given that you're on Ryzen I wouldn't be surprised that there's a mis-compilation issue somewhere.
(In reply to Elvis Pranskevichus from comment #6) > Have you tried a newer GCC version? Given that you're on Ryzen I wouldn't > be surprised that there's a mis-compilation issue somewhere. Yes, I've tried gcc-6.3.0 and changed to --march=znver1, however it makes no difference.
I just realised that I called node when testing the working directory, not ./node, so I was probably using my nodejs version of the binary instead (i.e., the binary was probably corrupted even before it was merged to the live system).
For some reason I didn't notice the message when emerging electron the first time, but it looks like grkernsec is the the issue here.
