Open Bug 553581 Opened 10 years ago Updated 1 year ago

AVG Safe Search Possibly causes crash at [@ XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) ]

Categories

(Core :: General, defect, P3, critical)

1.9.2 Branch
x86
Windows 7
defect

Tracking

()

Tracking Status
blocking2.0 --- -
firefox-esr60 --- affected
firefox64 --- affected

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: crash, Whiteboard: [crashkill][explosive])

Crash Data

volume on this is up 5x since the first of March, with a bug jump on 3/15

date XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallModecrashes
20100301-crashdata 195 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100302-crashdata 205 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100303-crashdata 241 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100304-crashdata 269 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100305-crashdata 429 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100306-crashdata 409 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100307-crashdata 482 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100308-crashdata 356 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100309-crashdata 391 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100310-crashdata 438 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100311-crashdata 414 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100312-crashdata 499 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100313-crashdata 562 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100314-crashdata 647 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100315-crashdata 1151 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100316-crashdata 1124 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100317-crashdata 1090 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100318-crashdata 1133 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100319-crashdata 951 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100320-crashdata 1027 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
20100321-crashdata 989 XPCWrappedNative::CallMethod.XPCCallContext...XPCWrappedNative::CallMode
Whiteboard: [crashkill] → [crashkill][explosive]
In a twitter conversation with an affected user, he reported that disabling the AVG Safe Search add-on fixed the issue. See http://twitter.com/Paul_Yates
Summary: Crash Report [@ XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) ] → AVG Safe Search Possibly causes crash at [@ XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) ]
Greg, can AVG help check this out?
Yes, we are looking at.  Advisory support for Gmail was added in early March.
Currently this looks like an incomplete code update.  The specific AVG modules are too old to support Gmail.  Checking with install/update team in AVG.
Assignee: nobody → greg.mosher
Can't block on this.  Feel free to argue, tho.  :)
blocking2.0: ? → -
Crash Signature: [@ XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) ]
Crash Signature: [@ XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) ] → [@ XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) ] [@ XPCWrappedNative::CallMethod ]
We still have 5 to 10 crashes a day on this one on release and esr, Windows only (7/8/10). Removing the assignee as it was set 8 years ago, setting as P3 as the crash volume today is low, mostly on Windows 7
Assignee: greg.mosher → nobody
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.