DLSS-G plugin (sl.dlss_g 2.12.128) calls into host from DllMain during ExitProcess, crashing Call of Duty: Modern Warfare 4 on exit
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start by reading the DLSS-G teardown path in sl.dlss_g.dll and how it calls host callbacks through sl.common.dll during DLL_PROCESS_DETACH; the report provides no source files or tests to locate that path. Compare shutdown behavior with and without Frame Generation enabled, and determine whether teardown calls into the host during ExitProcess. Done means the reproducible exit crash is resolved without breaking campaign handoff.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
In Call of Duty: Modern Warfare 4 (Steam, PC), the hub process cod.exe crashes on every exit when DLSS Frame Generation is enabled. The crash is on the main thread inside sl.dlss_g.dll's DllMain during DLL_PROCESS_DETACH: the plugin calls through sl.common.dll back into the host executable, which then dereferences a null pointer.
The user-visible effect is severe: the game exits the hub process to hand over to a separate campaign executable, so this crash blocks the campaign from ever starting (the preloaded campaign process waits forever).
I can't tell from the outside whether this is host misuse (e.g. the title not calling slShutdown() before exit()) or the plugin doing teardown work that calls host callbacks from DllMain at process exit. Filing here because the crashing path originates in the DLSS-G plugin and so NVIDIA can assess it or relay it to the title's developer. It has also been reported to Activision.
Environment
- Streamline DLLs shipped with the game:
sl.interposer.dll,sl.common.dll,sl.dlss_g.dllall 2.12.128.0 (production);nvngx_dlssg.dll310.7.128.0 - GPU: GeForce RTX 4060 8 GB, driver 32.0.16.2114 (621.14)
- OS: Windows 11 Home 10.0.26300.9974
- Title: Call of Duty: Modern Warfare 4, Steam app 1938090, build 26447320, engine version 2.5.0, changelist 29836037 (D3D12)
- Reflex enabled, DLSS Super Resolution enabled
Reproduction
- Enable DLSS Frame Generation in the game's graphics settings and restart the game.
- From the main menu, click Campaign (the hub process calls
exit()to hand off tosp26-cod.exe). cod.execrashes during process shutdown.
Frequency: 23+ occurrences between Nov 6 and Nov 11, 2026, identical stack across every dump examined. With Frame Generation disabled from startup, the process exits cleanly (1 of 1 so far). Disabling it mid-session and then exiting still crashes.
Stack (main thread, most recent frame first)
Symbols for sl_* and cod are export-relative only (no private PDBs), so offsets are the reliable part.
cod+0x7dd99a6 <-- 0xc0000005, access violation reading address 0x0
cod+0x8164857
sl_common!slGetPluginFunction+0x26ae9
sl_common!slGetPluginFunction+0x2acb2
sl_dlss_g+0x41ff7
sl_dlss_g+0x1539d
sl_dlss_g!slGetPluginFunction+0xf8e6
sl_dlss_g!slGetPluginFunction+0xe74d
sl_dlss_g!slGetPluginFunction+0x2596
sl_dlss_g+0x50045
sl_dlss_g+0x4f5d7
sl_dlss_g!DllMain+0x10e
sl_dlss_g!slGetPluginFunction+0xfc47 (CRT DLL entry)
ntdll!LdrShutdownProcess+0x17f
ntdll!RtlExitUserProcess+0x9e
kernel32!ExitProcess+0xb
ucrtbase!common_exit+0xc7
cod+0xacab353 (host calling exit())
Before the title's Nov 10 patch the faulting host address was cod+0x7da49f6, with the same sl_dlss_g / sl_common frames.
Note for anyone matching this against telemetry: Windows Error Reporting records it as 0xc000000d in ntdll.dll. That is a secondary failure. The host's unhandled exception filter calls WerReportSubmit, which loads netprofm.dll, whose DllMain fails in CreateThreadpoolTimer because the process is already shutting down.
Workaround
Disable DLSS Frame Generation and restart the game before exiting the hub.
Dumps
Full user-mode dumps (180-300 MB each) are available; I'd rather share them privately than attach them publicly since they contain process memory.
- Lenguaje dominante
- C
- Estrellas
- 1.4k
- Forks
- 174
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NVIDIA-RTX/Streamline
-
Title: Vulkan: VK_FORMAT_R8_UNORM missing in Vulkan::getFormatPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
NVIDIA-RTX/Streamline#133 ·
-
sl.log folder makes it hard to integrate, as many developer has *.log in the exclude filter for git/p4.Posiblemente ocupada @Dragon31337 la tomó hace 72 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
NVIDIA-RTX/Streamline#121 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
NVIDIA-RTX/Streamline#120 ·
-
C++23 issueAbiertobug triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
NVIDIA-RTX/Streamline#111 · 1 comentario ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
NVIDIA-RTX/Streamline#134 ·
Todos los issues de NVIDIA-RTX/Streamline
Issues similares
-
ecs_ptr_from_json does not free the buffer of a string longer than 256 bytes on two error pathsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
SanderMertens/flecs#2444 ·
Los mantenedores suelen responder en 1 día
-
Status: Opened
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
espressif/esp-eth-drivers#201 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
libsdl-org/SDL#16788 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
cisco/ChezScheme#1110 ·
Los mantenedores suelen responder en 1 día