8278309: [windows] use of uninitialized OSThread::_state

Backport-of: 54993b13078ceb05736bb0e1d7ed7415c390442e
openjdk · Feb 10, 2022 · 5fb0e1a · 5fb0e1a · openjdk-notifier · Feb 10, 2022
1 parent c9a3110
commit 5fb0e1a
Showing 1 changed file with 4 additions and 1 deletion.
diff --git a/src/hotspot/os/windows/os_windows.cpp b/src/hotspot/os/windows/os_windows.cpp
@@ -597,6 +597,9 @@ bool os::create_thread(Thread* thread, ThreadType thr_type,
     return false;
   }
 
+  // Initial state is ALLOCATED but not INITIALIZED
+  osthread->set_state(ALLOCATED);
+
   // Initialize the JDK library's interrupt event.
   // This should really be done when OSThread is constructed,
   // but there is no way for a constructor to report failure to
@@ -692,7 +695,7 @@ bool os::create_thread(Thread* thread, ThreadType thr_type,
   osthread->set_thread_handle(thread_handle);
   osthread->set_thread_id(thread_id);
 
-  // Initial thread state is INITIALIZED, not SUSPENDED
+  // Thread state now is INITIALIZED, not SUSPENDED
   osthread->set_state(INITIALIZED);
 
   // The thread is returned suspended (in state INITIALIZED), and is started higher up in the call chain