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 }}
This repository has been archived by the owner on Mar 15, 2021. It is now read-only.
We are hitting a significant number of Crashes in Chrome that are 100% correlated with obs-virtualcam-model64.dll. The crash call stack looks like this:
Note that the call stack is speculative once it gets into obs-virtualcam-module64.dll since 64-bit stack walking relies on metadata from the DLL or PDB. I tried to find obs-virtualcam-module64.dll in the latest release but it is not there, and I'd really need the symbols to be able to file an entirely accurate bug report.
Roughly 67% of the crashes are happening with the 26.0.0.0 version of the DLL, and 15% of the crashes are with the 26.1.0.0 version. That is, it appears that the bug has not been fixed in 26.1.0.0. The call stack above is from the 26.1.0.0 version, Timestamp: Mon Dec 14 09:57:59 2020 (5FD7C3C7).
If you can share a DLL and PDB for that version (or for 26.0.0.0) then I can give a more complete call stack. From our side, the actual crashing line is this one:
From analysis of the source, machine code, and debug information it appears that receiver_ is NULL, which suggests that the Receive method was called incorrectly.
It is possible that this is a bug in Chrome, but since the crash is 100% correlated with obs-virtual-cam we are assuming that it is not.
Thoughts?
The text was updated successfully, but these errors were encountered:
For our reference, this correlates to crbug.com/1137308. Unfortunately that bug has restricted access so you won't be able to see it although we could probably CC a team member to give them access to it.
We are hitting a significant number of Crashes in Chrome that are 100% correlated with obs-virtualcam-model64.dll. The crash call stack looks like this:
The actual crash is a read from location 0.
Note that the call stack is speculative once it gets into obs-virtualcam-module64.dll since 64-bit stack walking relies on metadata from the DLL or PDB. I tried to find obs-virtualcam-module64.dll in the latest release but it is not there, and I'd really need the symbols to be able to file an entirely accurate bug report.
Roughly 67% of the crashes are happening with the 26.0.0.0 version of the DLL, and 15% of the crashes are with the 26.1.0.0 version. That is, it appears that the bug has not been fixed in 26.1.0.0. The call stack above is from the 26.1.0.0 version, Timestamp: Mon Dec 14 09:57:59 2020 (5FD7C3C7).
If you can share a DLL and PDB for that version (or for 26.0.0.0) then I can give a more complete call stack. From our side, the actual crashing line is this one:
https://source.chromium.org/chromium/chromium/src/+/master:media/capture/video/video_capture_device_client.cc;l=616?q=VideoCaptureDeviceClient::OnIncomingCapturedBufferExt
From analysis of the source, machine code, and debug information it appears that receiver_ is NULL, which suggests that the Receive method was called incorrectly.
It is possible that this is a bug in Chrome, but since the crash is 100% correlated with obs-virtual-cam we are assuming that it is not.
Thoughts?
The text was updated successfully, but these errors were encountered: