Blocklist old versions of Acrobat Reader due to crashes [@ UserCallWinProcCheckWow]




8 years ago
2 years ago


(Reporter: whimboo, Unassigned)


(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)




8 years ago
With bug 531551 we track the #1 topcrasher for Firefox 3.6. As David Baron proposed over there this bug should handle the blocklist work for the Plugin.

David, which versions should be blocked in detail? Are those only the following or all releases of 8.1 and 9.0?

19% (837/4360) vs.   1% (1200/97654) 
14% (631/4360) vs.   1% (919/97654)
16% (695/4360) vs.   1% (1287/97654)

Comment 1

8 years ago
Chris, would you have time to check which versions of Acrobat reader should be blocklisted?

Comment 2

8 years ago
as mentioned in we can't do good version check against acrobat since they haven't been updating the version info after critical security updates.  

adobe plans to start doing this with the next release.  after that we should be able to block old versions.
Are there identifiable and unique older DLLs that we can block?

Comment 4

8 years ago
I'm seeing about 200-270 crashes per day from , and with this stack signature  and general users comments about what looks like pdf interaction to view and print out US tax returns.  I think there might be several parts of their tax filing app that might tickle pdf interaction bugs.

an example is


I suspect volume on this could increase as the April 15th tax filing deadline in the US approaches.

I can't think of any ideas other than maybe getting intuit to publish warnings about installing the latest version of acrobat before starting the filing process.   maybe we can also contact them to see if there is a way create reproducible test cases with the pdf interaction.

Comment 5

8 years ago
In general the UserCallWinProcCheckWow are mostly 3.6.x.

checking --- 20100328-crashdata.csv UserCallWinProcCheckWow
release total-crashes
              UserCallWinProcCheckWow crashes

3.5.8   34753   271     0.00779789
3.0.18  10964   91      0.00829989
3.6.2  212098  10906   0.0514196

that seems to hold up for these turbotax UserCallWinProcCheckWow crashes.  about 99% of them are 3.6 or 3.6.2.

Comment 6

8 years ago
oops, I guess comment 4 and 5 should go over in bug 531551, not this bug to block list.

Comment 7

8 years ago
old versions of reader could be blocked now since the latest update has proper version info 

Version 9.3.2 of Reader now includes 9.3.2 in the name and this will be updated
for each new version.
Version 8.2.2 of Reader now includes 8.2.2 in the name and will be updated for
each new version.

maybe start with soft blocking of all versions earlier than these and see if we can get people moving.


8 years ago
Blocks: 517203

Comment 10

8 years ago
(In reply to comment #7)
> maybe start with soft blocking of all versions earlier than these and see if we
> can get people moving.

is blocklisting still on the table?
~#70 crash for thunderbird 3.0.6

Comment 11

8 years ago
If so, please do the same for SeaMonkey, this signature is the #1 topcrash for newly released SeaMonkey 2.0.8 (even though it does not have a very high count - I guess we are just very stable now).

Comment 12

7 years ago
UserCallWinProcCheckWow is the top crash for 3.6. Can we get the block list in place for older versions of Acrobat and see how it affects the relative placement and frequency of this signature? Seems a rather large potential return for little investment.

Comment 13

7 years ago
I guess a blocklist wouldn't help, because Firefox crashes on the latest versions of the Acrobat plugin, not on the old ones. older 8.x plugins are working fine, but who wants to use them..? The problem is big enough that I turned away from Firefox to Chrome where I can use the internal pdf viewer instead of the Acrobat plugin and thus avoid the crashes.

Comment 14

6 years ago
There's a spike in crashes from 15.0a1/20120503:

It's still correlated to old versions of Acrobat Reader:
* 5/6:
  UserCallWinProcCheckWow|EXCEPTION_ACCESS_VIOLATION_EXEC (12 crashes)
     67% (8/12) vs.   1% (14/2762) nppdf32.dll
         25% (3/12) vs.   0% (3/2762)
          8% (1/12) vs.   0% (1/2762)
         33% (4/12) vs.   0% (6/2762)
* 5/8:
  UserCallWinProcCheckWow|EXCEPTION_ACCESS_VIOLATION_EXEC (20 crashes)
     60% (12/20) vs.   1% (35/2624) nppdf32.dll
         20% (4/20) vs.   0% (7/2624)
         10% (2/20) vs.   0% (2/2624)
          5% (1/20) vs.   0% (1/2624)
         25% (5/20) vs.   0% (12/2624)
As far as I can see, the current blocks cover these crashy versions.
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME


2 years ago
Product: → Toolkit
You need to log in before you can comment on or make changes to this bug.