Chrome Browser Crash when starting screen sharing

We have a wide user base using Jitsi ou our own servers. Two of the users recently started to report browser crashes when enabling screen sharing in a jitsi room. I tried with our own server and with meet.jit.si. Anyone experimenting the same issue? For information: I have completely reset Chrome during the tests and even created a new windows user. It still happens. OS: Windows 10, Browser: Chrome.

Similar issue started today. Just pressing the Screenshare button causes the browser to close instantly. All tabs get closed and the browser offers to restore tabs when I open it again.

Happens not only in Brave, but also Chrome and Vivaldi. As if the problem is deeper than a single browser.

Most interestingly, it does not happen on my other computer. The only thing I could think of (although probably unrelated) is my upgrade. I put a new ssd in my pc and updated my motherboard’s bios yesterday. But could it cause something like this?

Using meet.jit.si

exactly the same with me.
Win10, latest Chrome

Me too, every time I try to share screen Chrome closes by itself.

I am facing the same issue on my windows 10 laptop on chrome

Same here …both with Chrome and Edge. It works with Firefox

Same for me with Chrome and Windows 10

Yes, can confirm that this is happening on my PC as well this past week.
Chrome Version 81.0.4044.129 (also happens in the new Chromium-based Edge)
Windows 10 Pro Version.1909
Happens on all jitsi servers, but does not crash with other screen sharing sites/applications. Other users are having no problems, so not sure if it was caused by some update to Chrome or Windows or what.

Edge crash report is indicating Access Violation:
Sig[0].Name=Application Name
Sig[0].Value=msedge.exe
Sig[1].Name=Application Version
Sig[1].Value=81.0.416.68
Sig[2].Name=Application Timestamp
Sig[2].Value=5ea7ea23
Sig[3].Name=Fault Module Name
Sig[3].Value=msedge.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=81.0.416.68
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5ea7ea23
Sig[6].Name=Exception Code
Sig[6].Value=c0000005 ←exception code for access violation
Sig[7].Name=Exception Offset
Sig[7].Value=00000000034132df

Following is crash dump analysis:
DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT: (.ecxr)
rax=0000013d44b30024 rbx=0000013d4c23ff08 rcx=0000013d44b30024
rdx=ffffffffffffffe0 rsi=0000013d4bfb21e0 rdi=0000002c6e1ff358
rip=00007ffc36cc32df rsp=0000002c6e1ff290 rbp=9ddfea08eb382d69
r8=0000002c6e1ff2d8 r9=0000000000000000 r10=00000fff86de88f5
r11=ffffffffffffffff r12=0000013d4bfb2218 r13=4be26cdc90d70073
r14=0000013d4c23ffa8 r15=b492b66fbe98f273
iopl=0 nv up ei ng nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010286
msedge_7ffc338b0000!IsSandboxedProcess+0x472adf:
00007ffc36cc32df 488b7c11d8 mov rdi,qword ptr [rcx+rdx-28h] ds:0000013d44b2ffdc=???
Resetting default scope

FAULTING_IP:
msedge_7ffc338b0000!IsSandboxedProcess+472adf
00007ffc`36cc32df 488b7c11d8 mov rdi,qword ptr [rcx+rdx-28h]

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffc36cc32df (msedge_7ffc338b0000!IsSandboxedProcess+0x0000000000472adf)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000013d44b2ffdc
Attempt to read from address 0000013d44b2ffdc

DEFAULT_BUCKET_ID: INVALID_POINTER_READ

PROCESS_NAME: msedge.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000013d44b2ffdc

READ_ADDRESS: 0000013d44b2ffdc

FOLLOWUP_IP:
msedge_7ffc338b0000!IsSandboxedProcess+472adf
00007ffc`36cc32df 488b7c11d8 mov rdi,qword ptr [rcx+rdx-28h]

BUGCHECK_STR: INVALID_POINTER_READ

WATSON_BKT_PROCSTAMP: 5ea7ea23

WATSON_BKT_PROCVER: 81.0.416.68

WATSON_BKT_MODULE: msedge.dll

WATSON_BKT_MODSTAMP: 5ea7ea23

WATSON_BKT_MODOFFSET: 34132df

WATSON_BKT_MODVER: 81.0.416.68

MODULE_VER_PRODUCT: Microsoft Edge

BUILD_VERSION_STRING: 10.0.18362.778 (WinBuild.160101.0800)

MODLIST_WITH_TSCHKSUM_HASH: 351fca560abe909ae59a8cb91e39203622229857

MODLIST_SHA1_HASH: 9168d53a49f14b8ac153acb656d05907a514e086

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

DUMP_FLAGS: 94

DUMP_TYPE: 1

APP: msedge.exe

ANALYSIS_SESSION_HOST: JAY-PC

ANALYSIS_SESSION_TIME: 05-01-2020 00:31:38.0296

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

THREAD_ATTRIBUTES:
OS_LOCALE: ENU

PROBLEM_CLASSES:

INVALID_POINTER_READ
Tid [0x14f8]
Frame [0x00]: msedge_7ffc338b0000!IsSandboxedProcess

LAST_CONTROL_TRANSFER: from 00007ffc395ced62 to 00007ffc36cc32df

STACK_TEXT:
0000002c6e1ff290 00007ffc395ced62 : 0000000000000000 00007ffc3395288c 0000000000000000 0000000000000000 : msedge_7ffc338b0000!IsSandboxedProcess+0x472adf
0000002c6e1ff310 00007ffc33954781 : 0000cac482000101 0000000000000000 0000000000000000 0000000000000004 : msedge_7ffc338b0000!ExportSpartanCookies+0x1bc531a
0000002c6e1ff400 00007ffc33951ff4 : 0000000000000000 0000013d00000000 ffffffff00000000 0000013d3fc92640 : msedge_7ffc338b0000!ChromeMain+0x9d4a3
0000002c6e1ff4d0 00007ffc33951db1 : 000000381b264d58 00000000000002ea 0000000000003dff 00007ffc9d999449 : msedge_7ffc338b0000!ChromeMain+0x9ad16
0000002c6e1ff600 00007ffc33a109e6 : 0000000000000000 0000000000000000 0000013d44675410 0000000000000001 : msedge_7ffc338b0000!ChromeMain+0x9aad3
0000002c6e1ff690 00007ffc3395f976 : 0000000000000002 0000000000000008 0000000000000008 00007ffc3afbdf38 : msedge_7ffc338b0000!ChromeMain+0x159708
0000002c6e1ff750 00007ffc33951c17 : 0000002c6e1ff8d0 0000000000000000 0000013d4c087160 00007ffc338b7149 : msedge_7ffc338b0000!ChromeMain+0xa8698
0000002c6e1ff7a0 00007ffc33951854 : 0000002c6e1ff868 00007ffc36377761 0000000000000000 0000000000000000 : msedge_7ffc338b0000!ChromeMain+0x9a939
0000002c6e1ff800 00007ffc339506ce : 000000000000001d 0000013d4c087150 0000000000000000 0000013d4c087150 : msedge_7ffc338b0000!ChromeMain+0x9a576
0000002c6e1ff8b0 00007ffc363a0861 : 0000013d419f2c20 00007ffc9dbf1db0 0000000000000000 0000000000000000 : msedge_7ffc338b0000!ChromeMain+0x993f0
0000002c6e1ff930 00007ffc9dbe7bd4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : msedge_7ffc338b0000!CrashForExceptionInNonABICompliantCodeRange+0x971db1
0000002c6e1ff9b0 00007ffc9f30ce51 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14
0000002c6e1ff9e0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21

THREAD_SHA1_HASH_MOD_FUNC: bde95dd69f7e30da2411b2dcaa98cd194dc953ab

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9ccf159e43b66458d0d4d30d55298a30a148e206

THREAD_SHA1_HASH_MOD: 7d5d2479485ec180a4a1964bb2fe1d15f801cf1e

FAULT_INSTR_CODE: 117c8b48

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: msedge_7ffc338b0000!IsSandboxedProcess+472adf

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: msedge_7ffc338b0000

IMAGE_NAME: msedge.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 5ea7ea23

STACK_COMMAND: .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_msedge.dll!IsSandboxedProcess

BUCKET_ID: INVALID_POINTER_READ_msedge_7ffc338b0000!IsSandboxedProcess+472adf

PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ_msedge_7ffc338b0000!IsSandboxedProcess+472adf

BUCKET_ID_OFFSET: 472adf

BUCKET_ID_MODULE_STR: msedge_7ffc338b0000

BUCKET_ID_MODTIMEDATESTAMP: 5ea7ea23

BUCKET_ID_MODCHECKSUM: 87b9038

BUCKET_ID_MODVER_STR: 81.0.416.68

BUCKET_ID_PREFIX_STR: INVALID_POINTER_READ_

FAILURE_PROBLEM_CLASS: INVALID_POINTER_READ

FAILURE_EXCEPTION_CODE: c0000005

FAILURE_IMAGE_NAME: msedge.dll

FAILURE_FUNCTION_NAME: IsSandboxedProcess

BUCKET_ID_FUNCTION_STR: IsSandboxedProcess

FAILURE_SYMBOL_NAME: msedge.dll!IsSandboxedProcess

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/msedge.exe/81.0.416.68/5ea7ea23/msedge.dll/81.0.416.68/5ea7ea23/c0000005/034132df.htm?Retriage=1

TARGET_TIME: 2020-04-30T14:51:59.000Z

OSBUILD: 18363

OSSERVICEPACK: 778

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 256

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt SingleUserTS

USER_LCID: 0

OSBUILD_TIMESTAMP: 1987-11-30 05:07:31

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.18362.778

ANALYSIS_SESSION_ELAPSED_TIME: 340d8

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:invalid_pointer_read_c0000005_msedge.dll!issandboxedprocess

FAILURE_ID_HASH: {230fca1f-b805-b00e-25d7-6b8ef8211975}

Followup: MachineOwner

Screen sharing works fine on an older version of Jitsi (~ 4 weeks ago) on Chrome 81.0.4044.129.

Seems like an issue with newer Jitsi build.

I was told to try this in a different thread. This also crashes my browsers.

https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#6082796372370036

1 Like

I’m having the same issue. Not only with Jitsi. Windows 10, latest Chrome, it crashes when trying to share the screen for Jitsi and also for my NextCloud instance, and also for the above linked webrtc-experiment site. This leads me to believe it is a Windows10/Chrome/WebRTC issue rather than something in the NextCloud (Spreed) or Jitsi codebases. Firefox works fine. Edge… actually seems to be sharing just fine. Sometimes Chrome works fine, but once it has a problem, the problem persists at least until a reboot.

It has been especially annoying in my case because Chrome is the only browser that seems to work with the new Canon webcam driver beta… so I have to pick between being able to screenshare or being able to use the nice camera.

In my case, Chrome crashes after you stop sharing the screen (or a window). There are black triangles in the Chrome window or it turns completely black. You can’t click anything anymore. It only helps to close the chrome window via taskbar => right mouse => close window and dial into the meeting again.

I use as client the latest Windows 10 Version 1909 with all updates installed and the latest Google Chrome version 81.0.4044.138 and as server the official Debian package of Jitsi:
apt-cache policy jitsi-meet | grep Installed
Installed: 2.0.4468-1

Yes, I can report the same. I have not systematically troubleshot but it appears to happen after the first share. That is, I can share my screen fine. Then I stop and try to share again and it crashes. Briefly looking at the trace above, it looks like a pretty typically pointing to a memory location that doesn’t exist error.

I wonder if this was introduced with the very useful presenter mode functionality. I do trust it is being treated as a P1 bug. Thanks.

Hello, all. The problem seemed better today but not completely gone. I was doing a Jitsi training session and probably shared screen 20 times. I crashed only once.

@ALVK have you managed to get a resolution to the webrtc issue ?

Hi. Yes, but unfortunately it happened on its own. Everything just started working, and I don’t know whether it was due to a browser or windows update or something else. I also stopped using jitsi a couple of weeks ago, so I don’t know whether it’s still true. It got broken and fixed so suddenly. I wouldn’t be surprised if it happened again…

Alas, the problem is still here in force. We had a Jitsi training session tonight and it was quite hampered. Most of the times we attempted to share screens, Chrome crashed. I don’t know if it’s a Chrome bug, a Jitsi bug, a WebRTC bug or something else but we do need some help. This will have people leaving for other products if we do not get this under control soon. Thanks.

1 Like

With actual Beta Chrome 84 it seems fixed. We tried several times and cant reproduce it with 84, while the same Clients with 83 are freezing, when one ends his Screen Sharing.

I can confirm that observation. The latest 83 version still has the problem but the beta 84 has been stable for me in several sessions.