I tested this on a second Kiosk application, and could reproduce the bug there to.
All you need to do is
- Display a text box
- Enter text into this
- Perform an action which causes the text box to be removed from the DOM
- Display the same text box or a different text box
- Focus on this text box

Then the application freezes. Your only option is to restart the application.

I have written a test application which demonstrates the problem.

This problem occurs when running in Kiosk Mode, and using the virtual keyboard. If you plug a keyboard in the problem doesn't happen. 

https://chrome.google.com/webstore/detail/chrome-defect-853617/jodmbnfjonbjlldmngcohmkkcdepfami?authuser=1

I've included the source code for this test application, and a video that demonstrates the defect.

Deleted: Chrome_Kiosk_Freeze_1280x720_2000.mp4 7.0 MB

	Chrome_Kiosk_Freeze_1280x720_2000.mp4 7.0 MB View Download

Deleted: defect-853617-demo-1.zip 1.4 KB

defect-853617-demo-1.zip 1.4 KB Download

case:16147933
debug logs: https://drive.google.com/open?id=1waFz9sRCVmxv4Chabl8AfIqHfKzznB8d
customer info: https://drive.google.com/open?id=1Xb5b-bUuCS1ZzfIrziYmA4dXevrN-NRfUHja9wnZVXo
Issue Time:   25/06/2018, between  9:50 and 9:52 AM, UTC +10

marcore: have you tried reproducing the problem on your end (please do so). Does this affect all devices or only x86_64? Once we have repro can we narrow scope of when issue started occuring? 56 - 67 is far to large a range to guess at a change that might be causing this issue.

@Jay, I don't have the same HW (sumo:  AOpen Chromebase Commercial), I've tried on my Chromebooks but I'm unable to reproduce.
no repro on:
Minnie: ChromeOS 66.0.3359.203 (32 bit) for this there is not 67 stable yet.
Glimmer: ChromeOS 67.0.3396.87 (64 bit)
peppy:  ChromeOS 67.0.3396.87 (64 bit)
nyan_blaze: ChromeOS 67.0.3396.87 (32 bit)

More information:
We originally tested this on an Acer Chromebase. We subsequently tested this on an AOpen Chromebase, and the defect happened there as well.

We then rolled the AOpen Chromebase back to Chrome OS version 64, and could no longer produce the problem.

Therefore, this error was introduced in ChromeOS version 65 or later.

Do the Chomebooks have built-in keyboards? That would explain why you cannot reproduce the problem on Chromebooks. This defect only manifests itself when there's no keyboard attached.

in the log ( for example ui/ui.20180625-095012 )
I see:
1,3060805632:23:47:01.283083] Native Client module will be loaded at base address 0x0000000000000000
E0624 23:47:03.715427       1 fst-model.cc:637] Failed to decompress file /mutable/fst/main_en_us_d3.dict_
[2655:2655:0625/094956.965612:ERROR:event_rewriter_chromeos.cc(416)] Device ID 3 is unknown.
[2655:2655:0625/094957.017153:ERROR:event_rewriter_chromeos.cc(416)] Device ID 3 is unknown.
[2655:2655:0625/094957.068755:ERROR:event_rewriter_chromeos.cc(416)] Device ID 3 is unknown.
[2655:2655:0625/094957.120162:ERROR:event_rewriter_chromeos.cc(416)] Device ID 3 is unknown.
[2655:2655:0625/094957.171577:ERROR:event_rewriter_chromeos.cc(416)] Device ID 3 is unknown.

I can always reproduce that on buddy. ++example of "Good" behavior: https://drive.google.com/open?id=19tT5S8MeGtM0XsdqPl_3Uj1GiFpQmDru

And also performed bisect:

Good: 10463.0.0 	67.0.3362.0
Bad:  10464.0.0	        67.0.3363.0

Browser changes:
https://chromium.googlesource.com/chromium/src/+log/67.0.3362.0..67.0.3363.0?n=10000

ChromeOS changes:
https://crosland.corp.google.com/log/10463.0.0..10464.0.0

Jay, please help to find proper suspect (we don't have full visibility to above)

The customer has provided additional information below.

- What kind of monitor is (Brand and model)?: 
Customer has reproduced this problem on an AOpen ChromeBase Commercial (WT22-FBG) and an Acer ChromeBase (DC211HQ) as well. (http://www.aopen.com/au/chromebase-commercial). 

- How is connected to the ChromeBox (HDMI, DVI)? 
These are all in one units - the processor is embedded into the screen.

I am not able  to reproduce the customers issue on M69 dev using Aopen chromebase(Veyron-Tiger). After using the customers provided application, I enter text in the boxes using the touch panel and proceed to remove the boxes. Device does not crash on my end.

I have tested this on the Chrome OS Beta release (68.0.3440.87).

The defect no longer appears in Kiosk mode. This has been fixed in both my test application and the production application.

It appears this was rectified somewhere between 67.0.3363.0 and 68.0.3440.87.

Marking as "Verified" based on c#14 and c#15. Please feel free to re-open the bug if this issue will appear again.