Gotomeeting Chrome extension causes browser to crash

bug

#1

I use GotoMeeting for a lot of purposes - since the beta allows one to install Chrome extensions on Brave, I installed the Gotomeeting chrome extension (which enabled screen sharing) on my version. However, upon installing the extension, as soon as I open gotomeeting.com/ on brave, the browser crashes.


#2

Do you mind adding details from chrome://version ? Does it crash with the extension installed and visiting site or without extension also it crashes by just visiting the site?


#3

It crashes with extension installed, visiting the site and then trying to share the screen using the website’s ‘Share Screen’ option.

Below is the dump of my chrome://version

Brave Software Inc

Copyright 2018 Brave Software Inc. All rights reserved.

Brave 0.55.13 Chromium: 70.0.3538.54 (Official Build) beta (64-bit)
Revision 4f8e578b6680574714e9ed3bb9f02922b4dde40d-refs/branch-heads/3538@{#937}
OS Windows
JavaScript V8 7.0.276.27
Flash (Disabled)
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.54 Safari/537.36
Command Line “C:\Program Files (x86)\BraveSoftware\Brave-Browser-Beta\Application\brave.exe” --enable-tab-audio-muting --disable-domain-reliability --disable-chrome-google-url-tracking-client --no-pings --enable-features=EnableEmojiContextMenu,DesktopPWAWindowing,fill-on-account-select,NewExtensionUpdaterService --disable-features=SharedArrayBuffer,DefaultEnableOopRasterization,VizDisplayCompositor --flag-switches-begin --flag-switches-end
Executable Path C:\Program Files (x86)\BraveSoftware\Brave-Browser-Beta\Application\brave.exe
Profile Path C:\Users\kulka\AppData\Local\BraveSoftware\Brave-Browser-Beta\User Data\Default
Variations c134752e-f685ead3

2c707b42-dcf7018a
411b6d4e-3f4a17df
d01ab0d3-419732d9
3e006338-3f4a17df
1a0d11d4-3f4a17df
16e0dd70-3f4a17df
ebeb14fc-3f4a17df
b7e2524c-3f4a17df
b3888d8d-afba0f91
6c18ba9d-3d98b302
8982496f-3f4a17df
61832c80-3f4a17df
cc20827f-77c422c
9041608a-3f4a17df
2db4845-ace4e138
74785582-3f4a17df
241fff6c-4eda1c57
9853922b-3f4a17df
125b7f68-3f4a17df
9ca1387e-3f4a17df
41e765a5-3f4a17df
1149accc-3f4a17df
776de70c-e0278d3d
ed9149a9-3f4a17df
a5cb8590-3f4a17df
34d450b1-3f4a17df
6c6c4f61-3f4a17df
76b48ab8-d4bd105c
c70841c8-a2567007
8ee5ed19-c3125ea2
74658432-fa79b94c
ed7ba060-3f4a17df
121ae2bc-65969d67
9e201a2b-3f4a17df
27212adc-27212adc
591576c8-3f4a17df
249dd49a-3f4a17df
5274eb09-3f4a17df
ceff87ec-3f4a17df
44827ee5-3f4a17df
8ca44045-3f4a17df
8f1e27f-3f4a17df
edbcf7c5-ddf1844d
77bbdddc-3f4a17df
5485fc4d-3f4a17df
de47491b-3f4a17df
93731dca-3f4a17df
9b4c4257-3f4a17df
8fa604e0-ace4e138
43f62d3b-3f4a17df
9e5c75f1-30e1b12b
6fa07eb4-7282ca76
2981bcb4-3f4a17df
2b86fd96-3f4a17df
5139837c-3f4a17df
4934552d-3f4a17df
7f8176d9-3f4a17df
296e6ad7-4cfc7c42
f7217a71-b2047178
23a898eb-fc93cf74
7a5ba892-3f4a17df
d1cd70a5-67592144
4ea303a6-3f4a17df
b19465ab-b19465ab
6e6e0c7e-3f17a7d8
95876445-400575af
d92562a9-441539fd
2b33233e-881ca6c9
4da5ae82-3f4a17df
56302f8c-2f882e70
14c5a050-61ceed18
2c1d398c-3f4a17df
cc54eb06-3f4a17df
b2612322-8a9180b2
cac0a91c-3f4a17df
df072bba-9a6c5085
f56e0452-3f4a17df
8576baf1-3f4a17df
f3ea30a0-3f4a17df
3038aa2e-3f4a17df
51b9b54d-3f4a17df
4bc337ce-535cb40a
9a2f4e5b-4bc735ae
1354da85-f1a864dc
17507c76-3f4a17df
6844d8aa-669a04e0
494d8760-3f4a17df
34baa302-cf4f6ead
587fa7b2-726d8ace
3a4029d-d7f231f3
bbb8f811-3f4a17df
94e68624-803f8fc4
cc73f8a1-3f4a17df
8834fcca-3f4a17df
11d91db8-d93a0620
ea0f933d-3f4a17df
493ac2c5-803f8fc4|


#4

Could you set the cookies to Allow all cookies from settings and see if this fixes the issue?