Created attachment 846806 [details] emerge info Emerging net-libs/nodejs-18.12.1 gives me the following error stacktrace In file included from ../deps/v8/src/profiler/heap-profiler.h:14, from ../deps/v8/src/heap/heap-inl.h:50, from ../deps/v8/src/objects/code-inl.h:14, from ../deps/v8/src/objects/property-cell-inl.h:11, from ../deps/v8/src/objects/dictionary-inl.h:15, from ../deps/v8/src/objects/contexts-inl.h:11, from ../deps/v8/src/execution/isolate-inl.h:9, from ../deps/v8/src/heap/factory-inl.h:12, from ../deps/v8/src/objects/lookup-inl.h:14, from ../deps/v8/src/objects/js-objects-inl.h:18, from ../deps/v8/src/objects/api-callbacks-inl.h:13, from ../deps/v8/src/objects/map-inl.h:9, from ../deps/v8/src/objects/instance-type-inl.h:11, from ../deps/v8/src/objects/js-proxy-inl.h:8, from ../deps/v8/src/objects/objects-inl.h:29, from ../deps/v8/src/compiler/osr.cc:9: ../deps/v8/src/debug/debug-interface.h:694:3: internal compiler error: Segmentation fault 694 | } | ^ Please submit a full bug report, with preprocessed source. See <https://bugs.gentoo.org/> for instructions. At the time I was rebuilding my system with glibc which had the nostrip feature. Removing the feature and rebuilding glibc merely changed the error message In file included from ../deps/v8/src/heap/factory.h:19, from ../deps/v8/src/ast/ast-value-factory.h:36, from ../deps/v8/src/ast/ast-value-factory.cc:28: ../deps/v8/src/heap/heap.h:260:70: internal compiler error: Segmentation fault 260 | int64_t total() { return total_.load(std::memory_order_relaxed); } | ^ Please submit a full bug report, with preprocessed source. See <https://bugs.gentoo.org/> for instructions.
Created attachment 846808 [details] build log
Created attachment 846810 [details] build environment
The error message in your attached build.log is different to the snippet you quoted wrt heap.h. This is not a good sign and implies possible memory issues. The fact there's no proper backtrace makes this more likely too. In fact, with ICEs, it's the main cause. But of course, real ICEs exist too. If this is reproducible, please follow https://wiki.gentoo.org/wiki/Gcc-ICE-reporting-guide, but I strongly recommend doing a memtest first.
Also... >The bug is not reproducible, so it is likely a hardware or OS problem.
I was verifying that it still crashed with various changes, which is why I got similar messages in multiple places
(In reply to Matt Hartley from comment #5) > I was verifying that it still crashed with various changes, which is why I > got similar messages in multiple places The problem is they're not very similar. It's a segfault and an ICE but the compiler doesn't even say which function inside GCC it died in. This sort of ICE (essentially no details, usually on a large C++ codebase, not on the same source file) is almost always hardware.
You can try without -freport-bug (counter-intuitive, I know) as sometimes that leads to worse information but it's not necessarily going to help.
oh, ok. Thank you so much. I'm not sure how to do a memtest, but will set that up. I rebooted and the crashes went away so you were right.
No worries at all, I've been there plenty of times - both "fake" and real ones (most recently finding my RAM had gone bad, just got ECC).
