fix: what a silly mistake again 🫠

We should call `Isolate::Enter` because we must bind the isolate to the thread
when evaluating the mod initially, but that doesn't mean it should only be
bound when evaluating. Naturally, we should invoke `Isolate::Enter` even when
the v8 isolate enters its loop again.

What a silly mistake again 😫

Author: nyannyacha

crates/base/src/deno_runtime.rs

@@ -387,12 +387,15 @@ impl DenoRuntime {
 
         let mut js_runtime = &mut self.js_runtime;
 
-        unsafe { js_runtime.v8_isolate().enter() };
-        let mut js_runtime = scopeguard::guard(&mut js_runtime, |it| unsafe {
-            it.v8_isolate().exit();
-        });
+        let mod_result_rx = {
+            unsafe { js_runtime.v8_isolate().enter() };
+            let mut js_runtime = scopeguard::guard(&mut js_runtime, |it| unsafe {
+                it.v8_isolate().exit();
+            });
+
+            js_runtime.mod_evaluate(self.main_module_id)
+        };
 
-        let mod_result_rx = js_runtime.mod_evaluate(self.main_module_id);
         let is_user_worker = self.conf.is_user_worker();
 
         #[cfg(debug_assertions)]
@@ -421,6 +424,11 @@ impl DenoRuntime {
             let get_current_cpu_time_ns_fn =
                 || get_thread_time().context("can't get current thread time");
 
+            unsafe { js_runtime.v8_isolate().enter() };
+            let mut js_runtime = scopeguard::guard(&mut js_runtime, |it| unsafe {
+                it.v8_isolate().exit();
+            });
+
             send_cpu_metrics_fn(CPUUsageMetrics::Enter(thread_id));
 
             current_cpu_time_ns = match get_current_cpu_time_ns_fn() {