chrome/test/data/reliability/known_crashes.txt - Issue 372018: Removed some crash suppressions:

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

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

Issue 372018: Removed some crash suppressions: (Closed)

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

OLD	NEW
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

(...skipping 115 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
126	126

127 # 23278	127 # 23278

128 SUBSTRING : webcore::xmlhttprequest::callreadystatechangelistener___webcore::xml httprequest::networkerror	128 SUBSTRING : webcore::xmlhttprequest::callreadystatechangelistener___webcore::xml httprequest::networkerror

129	129

130 # 23280	130 # 23280

131 SUBSTRING : webframeloaderclient::dispatchdidchangelocationwithinpage___webcore: :frameloader::continuefragmentscrollafternavigationpolicy___webcore::frameloader ::callcontinuefragmentscrollafternavigationpolicy___webcore::policycheck::call	131 SUBSTRING : webframeloaderclient::dispatchdidchangelocationwithinpage___webcore: :frameloader::continuefragmentscrollafternavigationpolicy___webcore::frameloader ::callcontinuefragmentscrollafternavigationpolicy___webcore::policycheck::call

132	132

133 # 23281	133 # 23281

134 REGEX : tabcontents::washidden___.*___tabcontents::~tabcontents	134 REGEX : tabcontents::washidden___.*___tabcontents::~tabcontents

135	135

136 # bug 23780

137 PREFIX : v8::internal::mayaccessprecheck

138

139 # 26506

140 PREFIX : webcore::eventtarget::fireeventlisteners___webcore::node::handlelocalev ents___webcore::node::dispatchgenericevent___webcore::node::dispatchevent

141

OLD	NEW

« no previous file with comments | « no previous file | no next file » | no next file with comments »