In bug #165159 I forgot to check that the ArrayBuffer obtained is always a new object, not a view onto the old. This is important because modifying the ArrayBuffer shouldn't modify the original custom section (there would also be lifetime issues).