You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Null pointer dereference in N_DoMessageLoopWork after CEF shutdown #559
Java_org_cef_CefApp_N_1DoMessageLoopWork calls Context::GetInstance()->DoMessageLoopWork() without null-checking GetInstance(). After N_Shutdown() calls Context::Destroy(), which sets g_context = nullptr, a Swing Timer event already queued in the AWT EDT can fire N_DoMessageLoopWork. GetInstance() returns null, the method call dereferences null, and the crash manifests as pthread_mutex_lock(0x10) because ThreadCheckerImpl::lock_ sits at offset 0x10 from the start of the Context object.
To Reproduce
This happened to me only one time when I was stress testing init/close sequence.
Expected behavior
Shutdown should be done without crash.
Versions:
OS: MacOS 26.x
Java Version: Eclipse Temurin 25.0.3
JCEF Version: g708dc14
CEF Version: 152.0.6
Fix
Add a null guard before calling DoMessageLoopWork().
Activity