Firefox crash epicplaygames.dll (Farmville)

RESOLVED WORKSFORME

Status

()

defect
--
critical
RESOLVED WORKSFORME
8 years ago
6 years ago

People

(Reporter: marcia, Unassigned)

Tracking

({crash})

9 Branch
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature, )

This bug was filed from the Socorro interface and is 
report bp-26929aef-66cb-48b4-a2b1-015292111212 .
============================================================= 

There are a bunch of these signatures that show up in a "contains" search. They are seen in the 9.0 betas but not in high volume. http://tinyurl.com/c7ujl2l - in the last week over a thousand crashes across all versions.

Most of the comments mention doing something in Farmville when they crash.

There are correlations to an addon and dll -

100% (63/63) vs.   0% (137/51284) epicPlayGames.dll
95% (60/63) vs.   0% (165/51284) textlinks@epicplay.com

We should watch this one for Firefox 9 to see if volume spikes.
The crash in question is a parent process crash, apparently from an addon using ctypes (probably incorrectly or there's a GC hazard).
http://biointegr8.blogspot.com/2011/11/fighting-epicplay.html has some information. I am still trying to hunt down where I can install the addon so I can try to reproduce the crash.
The crash reason in all reports is EXCEPTION_STACK_OVERFLOW, which seems a bit odd
given that there's only 65 or so stack frames in the crashes.
Crash Signature: [@ epicplaygames.dll@0xcfe7] → [@ epicplaygames.dll@0xcfe7] [@ epicplaygames.dll@0xcec7 ] [@ epicplaygames.dll@0xdc47 ] [@ epicplaygames.dll@0xdd37 ]
Summary: Firefox crash epicplaygames → Firefox crash epicplaygames.dll (Farmville)
It's true, but we just get that from the OS. It's possible they're doing something really stupid with the stack, or just getting unlucky and touching the guard page (which is probably what triggers that exception).
no crashes newer than version 20 in last 18 weeks with "epicplaygames" in signature.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.