Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-1605

Startup snapshot may not load when CPU features differ significantly

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 2.2.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      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.

            Assignee:
            anna.henningsen@mongodb.com Anna Henningsen
            Reporter:
            anna.henningsen@mongodb.com Anna Henningsen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: