For a given cut/copy event, Chrome prepares all possible outgoing mimetypes and submits this to the platform clipboard / pasteboard service. This is a completely reasonable approach for small snippets of text like the contents of this bug description.

If we still do this, when the user selects something like a 16mp image from a photo sharing site, this is not a good approach as encoding several . Make sure that when the copied/cut object is large and the clipboard service permits it that we don't block the UI thread prepping a bunch of large mime types of a clipboard object.