Issue metadata
Sign in to add a comment
|
Entire OS freezes when attempting to access Serial Port
Reported by
asheph...@datmedia.com.au,
Nov 14 2016
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36
Platform: 8743.83.o (Official Build) stable-channel panther
Steps to reproduce the problem:
1. Plug a USB to RS232 connector into your USB port
2. Run this code
let portPath = "/dev/ttyUSB0";
chrome.serial.connect(portPath, { bitrate: 9600 }, function() {});
3. Watch the entire system freeze
4. Unplug the adapter, and watch the system unfreeze
3.
What is the expected behavior?
For the OS to not freeze
What went wrong?
The OS become completely unresponsive. It froze.
Did this work before? Yes 5.43
Chrome version: 54.0.2840.93 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
We also tested the Chrome Store Application "Serial Control Signals".
This has exactly the same behavior.
https://chrome.google.com/webstore/detail/serial-control-signals/gmlopmidlcfikepbnklkochchhehjpak
,
Nov 14 2016
We can reproduce this error on both an Acer Chromebook and an Asus Chromebox
,
Nov 14 2016
,
Nov 15 2016
I can reliably reproduce this as well. This is a major issue. Attempting to use chrome.serial for any common FTDI device such as a BASIC Stamp or Arduino UNO locks up the chrome user interface. Needs to be made highest priority as production applications are broken.
,
Nov 15 2016
This is an critical issue!
We've just seen this symptom on two Chromebooks we own (which updated to Chrome OS v54) while using our Chrome App (that uses chrome.serial). Even plugging in a simple USB to RS-232 adapter (based on the FTDI chipset) causes the problem.
Our app is currently used by > 16k students to program our microcontroller hardware in class. This issue is a show stopper for them and us.
Chrome version: 54.0.2840.93 (64-bit)
Hardware: Acer Chromebook R11 CB5-132T
Toshiba Chromebook 2 CB35-B3340
,
Nov 16 2016
This may be a duplicate of (or at least related to) issue 644017 . https://bugs.chromium.org/p/chromium/issues/detail?id=644017
,
Nov 16 2016
Thank you. I concur, this is exactly the same issue as first reported back on Sept 4th, https://bugs.chromium.org/p/chromium/issues/detail?id=644017 - before v54 hit the streets in the stable channel. It may also be related to this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=652128 Which is bothersome because it seems to be jumping back and forth between fixed and broken yet again. For what it's worth, in the meantime I've verified that this was not a problem with v52.0.2743.116 and likely, though not yet proven, was not an issue in v53 either.
,
Nov 17 2016
This is also a critical issue for us. We use a USB/Serial BLE dongle that causes the OS to lock up sometime after querying the device list. Unplugging the dongle makes the UI 'unfreeze' and the user can carry on. However, the dongle is still not functional.
,
Nov 17 2016
I've found that the written fix for this issue has been committed into code starting with these versions: Stable: 54.0.2840.101 Beta: 55.0.2883.47 Developer: 56.0.2916.0 Now we just wait until "Stable" is released and propagates. NOTE: I have not verified that the fix resolves the problem.
,
Nov 17 2016
I have updated my Asus player to the later Stable Stream version of 54.0.2840.101. https://googlechromereleases.blogspot.com.au/2016/11/stable-channel-update-for-chrome-os_16.html I have tested my kiosk application against this version, and it appears to have fixed the issue. (ie it can communicate to TV screens via RS-232).
,
Nov 18 2016
I've tested 54.0.2840.101 on my machines as well and confirm that it fixes the problem. Thank you everyone!
,
Jun 7 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted