-
Notifications
You must be signed in to change notification settings - Fork 1.2k
OOM: DUCE+Channel.SyncFlush() #128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We’ll need a heap dump to investigate this further. Syncflush is a catch-all signature. This can be a real OOM, or a proxy for another kind of resource exhaustion (GDI handle, which incidentally has a per-session limit). |
Not sure I'll be able to get that, but WER may have it. Unfortunately, I don't have access to that data. It's coming from telemetry :/ |
I’ll see if I can find additional data and/or crash dumps. |
If it helps, they might be tied to its Store AppId: 9WZDNCRDMDM3. It has a bunch of crash data that's not available to me. It might be available to you. |
Hi @vatsan-madhavan, I'm encountering this issue as well, I've got a memory dump that was captured while our managed code in the UnhandledDispatcherException. How can I provide this to you? One thing to note, our application is using WindowsFormIntegration. |
I'm having the same crash with slightly different stack:
|
@vatsan-madhavan it's .NET framework |
I have been getting this for years in telemetry from hundreds of users, with slight variation of Stack Trace:
and
-Sometimes happening seconds after starting program and sometimes after hours of running. I have never caught it, but if there is something that an average user could do to help debug, or any other info, I can popup a message the next time exception contains SyncFlush() asking user to send more specific information |
Same issue in my application, in .net framework 4.6. |
I have the same issue but only on Windows Server 2012 and Windows 8. Exact same stacktrace as above. |
To everyone who has the same exception and callstack: You probably don't have the same issue, it may not be WPF's fault, and the WPF team can't help you without more detailed information. Please read https://docs.microsoft.com/en-us/troubleshoot/dotnet/framework/wpf-render-thread-failures for a fuller discussion. I'm closing this issue, as it's not actionable without more information. |
In my crash log this error precedes SyncFlush crash by a second
Unless I've made mistake in the logging, the window was minimized at the time of the crash and didn't have a focus. I also have that GDI handles count in moment of crash were 120 |
From telemetry, app crash:
The text was updated successfully, but these errors were encountered: