I can reproduce this if I type into a one of the fields and then tab through the other fields quickly while typing, and then clicking the button immediately after.

Here's some steps that I followed:
1) Click one of the fields to gain focus on it
2) Mouse over the button so it can be easily clicked
3) Start typing on the keyboard in the field
4) Press TAB
5) Continue typing
6) Repeat steps 3-5 rapidly
7) Click the button with the mouse

Tested with the EE-3.3.0_P01 jars on the IE11 test machine.

After disabling different parts of the ICEfaces bridge it seems the source of the problem is in the applying of the updates after clicking the Click here button. The arriving update has all the input elements with their value attribute missing (meaning that the text entry is empty), this will cause the browser to crash. If the value attributes are defined the browser will run fine over and over again.

Here's the proof that we're not the only ones to see this issue with IE11: http://connect.microsoft.com/IE/feedback/details/808033/ie11-two-reproducible-crashes-on-assigning-the-value-of-an-input-element-with-javascript

For now the only workable solution would be to set " " (one space) string into the value attribute and not the "" (empty) string.

Marking won't fix as this is an IE11 bug without an obvious solution that we can adopt.

Applications will have to adopt the suggested work-around of using single space values if necessary.