Brave crashes when a background process of an Extension uses WebRTC

[daviddias]

Got a SCTP error (transport used by WebRTC) a while after starting a js-ipfs node in a brave extension.

» npm run start

> [email protected] start /Users/imp/code/browser-laptop
> node ./tools/start.js --user-data-dir=brave-development --enable-logging --v=0 --enable-extension-activity-logging --enable-sandbox-logging --enable-dcheck

Crash reporting enabled
Loading: interplanetaryfilesystemuniverse component
Loading: jdbefljfgobbmcidnmpjamcbhnbphjnb component
Loading: jdbefljfgobbmcidnmpjamcbhnbphjnb component
Could not load background script 'content/scripts/sync.js'.
[93169:775:0822/172258.739131:ERROR:CONSOLE(26749)] "(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit.", source: http://localhost:8080/gen/app.entry.js (26749)
[93169:775:0822/172258.739228:ERROR:CONSOLE(26749)] "(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit.", source: http://localhost:8080/gen/app.entry.js (26749)
[93178:26627:0822/172307.472392:ERROR:adm_helpers.cc(62)] Failed to query stereo recording.
[93178:26627:0822/172738.759540:ERROR:sctptransport.cc(789)] SctpTransport->SendQueuedStreamResets(): Failed to send a stream reset for 1 streams: [0x00000016] Invalid argument


#
# Fatal error in ../../third_party/webrtc/base/platform_thread.cc, line 162
# last system error: 12
# Check failed: 0 == pthread_create(&thread_, &attr, &StartThread, this) (0 vs. 35)
#
#
2017-08-22 17:31:03.423 Brave Helper[93174:16936915] Couldn't set selectedTextBackgroundColor from default ()

This can be reproduced in ipfs-inactive@08b4f38

Other details are at: ipfs-inactive#1 (comment)

[daviddias]

This seems to be fairly reproducible, it just requires the brave browser to be running with something that uses WebRTC, example: IPFS integration.

I can disable the WebRTC transport for IPFS to mitigate the issue, but it does loose some of its flavor.

[NejcZdovc]

cc  @bridiver for his insight

[bridiver]

do you have a dump file or additional stack trace info?