Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(4)

Side by Side Diff: chrome/test/data/reliability/known_crashes.txt

Issue 330025: Add about:crash to known crashes. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/
Patch Set: Created 11 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # This file contains known patterns of crash signatures. One pattern per line. 1 # This file contains known patterns of crash signatures. One pattern per line.
2 # 2 #
3 # A crash signature is the concatenation of the top N functions, delimited by 3 # A crash signature is the concatenation of the top N functions, delimited by
4 # '___', in chrome.dll on the crash stack. All characters are lower case. 4 # '___', in chrome.dll on the crash stack. All characters are lower case.
5 # 5 #
6 # We use crash signature patterns as our list of known crashes. A crash 6 # We use crash signature patterns as our list of known crashes. A crash
7 # signature pattern is a string that can be used to identify a known crash. We 7 # signature pattern is a string that can be used to identify a known crash. We
8 # use the notion of patterns because crashes with the same root cause can often 8 # use the notion of patterns because crashes with the same root cause can often
9 # differ somewhat in their crash stacks. A pattern is intended to be a 9 # differ somewhat in their crash stacks. A pattern is intended to be a
10 # generalized, yet still identifying, form of a particular crash. Usually a 10 # generalized, yet still identifying, form of a particular crash. Usually a
11 # pattern will contain part of a crash signature, for example a prefix, but it 11 # pattern will contain part of a crash signature, for example a prefix, but it
12 # can be more sophisticated, such as a regular expression. See below for more 12 # can be more sophisticated, such as a regular expression. See below for more
13 # details. 13 # details.
14 # 14 #
15 # The format of known crashes in this file is as follows: 15 # The format of known crashes in this file is as follows:
16 # TYPE : PATTERN 16 # TYPE : PATTERN
17 # 17 #
18 # PATTERN: A crash signature pattern is a potentially identifying string that 18 # PATTERN: A crash signature pattern is a potentially identifying string that
19 # can be used to match a crash signature. 19 # can be used to match a crash signature.
20 # TYPE: The type of the pattern, indicates how the pattern should be matched 20 # TYPE: The type of the pattern, indicates how the pattern should be matched
21 # against crash signatures. Possible options are: 21 # against crash signatures. Possible options are:
22 # PREFIX: Match any signature beginning with this pattern. 22 # PREFIX: Match any signature beginning with this pattern.
23 # SUBSTRING: Match any signature containing this pattern. 23 # SUBSTRING: Match any signature containing this pattern.
24 # REGEX: Use this pattern as a regex to match against signatures. 24 # REGEX: Use this pattern as a regex to match against signatures.
25 # If the type is not listed, it defaults to PREFIX. 25 # If the type is not listed, it defaults to PREFIX.
26 26
27 # about:crash is a test page.
28 PREFIX : abouthandler::aboutcrash
29
27 # Any crash due to out of memory is ignored. 30 # Any crash due to out of memory is ignored.
28 PREFIX : `anonymous namespace'::onnomemory 31 PREFIX : `anonymous namespace'::onnomemory
29 32
30 # Mysterious crashes. Leave them for now. 33 # Mysterious crashes. Leave them for now.
31 34
32 # It is too broad to exclude all purecall related crashes. Thus here we filter 35 # It is too broad to exclude all purecall related crashes. Thus here we filter
33 # any purecall crash immediately after runtask. 36 # any purecall crash immediately after runtask.
34 SUBSTRING : purecall___messageloop::runtask 37 SUBSTRING : purecall___messageloop::runtask
35 REGEX : purecall___[^_]*___messageloop::runtask 38 REGEX : purecall___[^_]*___messageloop::runtask
36 REGEX : `anonymous namespace'::purecall$ 39 REGEX : `anonymous namespace'::purecall$
(...skipping 97 matching lines...) Expand 10 before | Expand all | Expand 10 after
134 SUBSTRING : webframeloaderclient::dispatchdidchangelocationwithinpage___webcore: :frameloader::continuefragmentscrollafternavigationpolicy___webcore::frameloader ::callcontinuefragmentscrollafternavigationpolicy___webcore::policycheck::call 137 SUBSTRING : webframeloaderclient::dispatchdidchangelocationwithinpage___webcore: :frameloader::continuefragmentscrollafternavigationpolicy___webcore::frameloader ::callcontinuefragmentscrollafternavigationpolicy___webcore::policycheck::call
135 138
136 # 23281 139 # 23281
137 REGEX : tabcontents::washidden___.*___tabcontents::~tabcontents 140 REGEX : tabcontents::washidden___.*___tabcontents::~tabcontents
138 141
139 # bug 23780 142 # bug 23780
140 PREFIX : v8::internal::mayaccessprecheck 143 PREFIX : v8::internal::mayaccessprecheck
141 144
142 # bug 25689 145 # bug 25689
143 PREFIX : skia::crashforbitmapallocationfailure___skia::platformcanvas::platformc anvas___webpluginproxy::setwindowlessbuffer___webpluginproxy::updategeometry___w ebplugindelegatestub 146 PREFIX : skia::crashforbitmapallocationfailure___skia::platformcanvas::platformc anvas___webpluginproxy::setwindowlessbuffer___webpluginproxy::updategeometry___w ebplugindelegatestub
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698