New issue
Advanced search Search tips

Issue 915528 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Device stuck and crashing the browser

Reported by thea...@gmail.com, Dec 16

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
There is no way to consistently reproduce that problem but basicly I played with the device and it started sending weird values in the event listener, values that were completly wrong, one event listener kept firing while the others stopped working and then the problem started.

What is the expected behavior?
The promise should resolve or reject and not freeze and if I'm running a line of code not making the browser stop responding and crash.

What went wrong?
The connect promise never resolves causing it to freeze and when I try to run the code again even before I get a chance to choose the device from the chooser the browser stops responding and then I have to crash it.

Not exactly sure, maybe has something to do with this issue - https://webbluetoothcg.github.io/web-bluetooth/#issue-f363405f.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version: 

Every time i tried to connect to the device i failed and made the browser crash (only that device btw).

After a couple of hours and enldess amount of crashes, I restarted my computer and I successfully managed to connect to it on the first try.
 
Labels: Needs-Triage-M71
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue...

@Reporter: Can you please provide details of the device and if possible provide a sample test file to triage this issue. Also provide crash id from "chrome://crashes".

Thanks..! 
Ping for details requested in comment #2.
Ping for details requested in comment #2.

Comment 5 by reillyg@chromium.org, Jan 16 (6 days ago)

Status: WontFix (was: Unconfirmed)
Without a crash ID there's no more investigation we can do here. Please reopen if you have a crash ID.

Sign in to add a comment