Segfault while running JS codeΒ #35581
Copy link
Copy link
Closed
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.
Description
Version: v14.13.0
Platform: Linux inspiron-3493-srinivasa 5.8.13-arch1-1 #1 SMP PREEMPT Thu, 01 Oct 2020 20:40:35 +0000 x86_64 GNU/Linux
What steps will reproduce the bug?
const v8=require('v8')
v8.getHeapSnapshot()
v8.getHeapSnapshot()What do you see instead?
Segfault
Additional information
GDB tells that the segfault occurs in this function
Backtrace:
#0 0x0000555555cf371e in v8::base::TemplateHashMapImpl<void*, void*, v8::base::HashEqualityThenKeyMatcher<void*, bool (*)(void*, void*)>, v8::base::DefaultAllocationPolicy>::Probe(void* const&, unsigned int) const ()
#1 0x000055555610f368 in v8::internal::StringsStorage::GetEntry(char const*, int) ()
#2 0x000055555610f6d2 in v8::internal::StringsStorage::GetName(v8::internal::Name) ()
#3 0x00005555561009a3 in v8::internal::V8HeapExplorer::AddEntry(v8::internal::HeapObject) ()
#4 0x00005555560f57ed in v8::internal::V8HeapExplorer::GetEntry(v8::internal::Object) ()
#5 0x0000555556101a48 in v8::internal::V8HeapExplorer::SetGcSubrootReference(v8::internal::Root, char const*, bool, v8::internal::Object) ()
#6 0x0000555556101ef4 in v8::internal::RootsReferencesExtractor::VisitRootPointers(v8::internal::Root, char const*, v8::internal::FullObjectSlot, v8::internal::FullObjectSlot) ()
#7 0x000055555613dd77 in v8::internal::ReadOnlyRoots::Iterate(v8::internal::RootVisitor*) ()
#8 0x0000555556100322 in v8::internal::V8HeapExplorer::IterateAndExtractReferences(v8::internal::HeapSnapshotGenerator*) ()
#9 0x00005555561015b3 in v8::internal::HeapSnapshotGenerator::GenerateSnapshot() ()
#10 0x00005555560f2a80 in v8::internal::HeapProfiler::TakeSnapshot(v8::ActivityControl*, v8::HeapProfiler::ObjectNameResolver*, bool) ()
#11 0x0000555555ac67b9 in node::heap::CreateHeapSnapshotStream(v8::FunctionCallbackInfo<v8::Value> const&) ()
#12 0x0000555555d0b637 in v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) ()
#13 0x0000555555d0b9fe in ?? ()
#14 0x0000555555d0c24a in ?? ()
#15 0x0000555555d0cba6 in v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) ()
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.
Activity
gireeshpunathil commentedon Oct 10, 2020
reported in #35559 too, though the callstack is different, so let us keep both.
gireeshpunathil commentedon Oct 10, 2020
able to reproduce.
A pattern that is observed is, main thread is active while
gcthreads are in the sweeping phase. Not sure if this is valid or not. I guess concurrent marking is valid, but not concurrent sweep?one of the sweeping thread has this stack:
addaleax commentedon Oct 11, 2020
I think closing this as a duplicate of #35559 would be fine.
gireeshpunathil commentedon Oct 11, 2020
root cause identified, and found to be same. fix will come by way of v8 changes. #35559 will track this. closing this.