Comment 2 for bug 1425055

I'm hitting the same issue in Pipelight using both 32-bit (Silverlight) and 64-bit (Flash) plugins on a whole pile of different systems. The address and stack trace are not consistent, but the one consistent feature is that the instruction pointer field (EIP on 32-bit Wine, rip on 64-bit Wine) is set to the same address as the reported address of the page fault. I rebuilt wine-staging from the provided Debian source packages using "-O0 -fno-stack-protector" and execstack, but this doesn't appear to have made any significant difference in the incidence of this issue. It occurs frequently at plugin initialization (i.e. page load) and behaves normally during playback.