-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
3
-
Not Needed
-
Iteration Velociraptor, Iteration Wendiceratops
Splitting this out from MONGOSH-1604:
# ./mongosh Failed to load the startup snapshot because it was built with a different version of V8 or with different V8 configurations. Expected tag 5d12db82, read a2ba2d4e ./mongosh[15469]: ../src/api/environment.cc:436:node::Environment* node::CreateEnvironment(node::IsolateData*, v8::Local<v8::Context>, const std::vector<std::__cxx11::basic_string<char> >&, const std::vector<std::__cxx11::basic_string<char> >&, node::EnvironmentFlags::Flags, node::ThreadId, std::unique_ptr<node::InspectorParentHandle>): Assertion `(isolate_data->snapshot_data()) != nullptr' failed.
For now, we can just disable startup snapshot support again. Long-term, we should follow up on https://github.com/nodejs/node/issues/42566#issuecomment-1735862123.
- is related to
-
MONGOSH-1642 mongosh 2.0.2 starts up significantly slower than 1.9.0
- Closed
-
MONGOSH-1540 Enable Node.js startup snapshot in mongosh
- Closed
- split from
-
MONGOSH-1604 "Illegal instruction" on mongosh 2.0.x execution on el7
- Closed
- split to
-
MONGOSH-1727 Include Node.js driver in startup snapshot
- Closed
- links to