Stream: StarlingMonkey

Topic: performance#timeOrigin not set during wizer pass

view this post on Zulip Tomasz Andrzejak (Jul 15 2025 at 08:00):

This is quite common error that I get from wizer for nodejs dependencies:

           2: 0x89db10 - <unknown>!std::__2::__throw_bad_optional_access[abi:v160000]()
           3: 0x8b0f2b - <unknown>!builtins::web::performance::Performance::timeOrigin_get(JSContext*, unsigned int, JS

The way I usually go around this issue is with this, rather dirty, StarlingMonkey patch:

extern "C" void perf_init_time_origin() {
  builtins::web::performance::Performance::timeOrigin.emplace(
      std::chrono::high_resolution_clock::now());
}

// performance time origin initialization function
extern "C" void __attribute__((weak)) perf_init_time_origin();

bool init_js() {
  ...
  if (perf_init_time_origin) {
    perf_init_time_origin();
  }
}

Is there a better way of doing this? It would be great if we could land a fix for this and I'm happy to work on a patch.

Last updated: Dec 06 2025 at 07:03 UTC