Chrome Version: 60.0.3107.0 (Official Build) dev (32-bit)
Chrome OS Version: 9582.0.0 (Official Build) dev-channel veyron_minnie
Chrome OS Platform: Asus C00P
Network info: not applicable

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)Update system to the dev-channel and reboot
(2)using udl2 device with a fullHD screen do
(3)plug udl2 device with a monitor to host, wait for pixels to appear on external display
(4)unplug udl2 device with a monitor from host, wait for system to remove monitor
(5) keep repeating sequence (3)-(5)

Expected Result:
No problems after performing of large number of plug/unplug cycle with a recognition by the system external monitor system recognition and displaying correct pixels on udl2-driven monitor

Actual Result:
After about 15 cycles of unplug/plug back udl2 driven monitor is corrupted and is displaying only black and white stripes. Monitor is correctly added to the system and is visible as external in display properties. Monitor is not refreshing, but displaying static black-white stripes

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
repro 2/2 but it require large number of retries. 
I used 32bit architecture as this is faster reproducible than in case of 64bit - so please take this under consideration during local reproduction

What is the impact to the user, and is there a workaround? If so, what is
it?
Unable to use udl2-driven display as part of system