Comment 3 for bug 1461256

This has nothing to due with the browser it has to do with the server sending a create action on the same object more than once. It is possible for this to occur in some weird race on how the triggers are fired from postgres and how they are processes by the region.

Easiest way and safest way to handle this is client side and check that the item does not already exist in the items array.