RESOLVED WONTFIX 66986
[chromium] Crash on screen unlock on XP due to cycle in layer tree 
https://bugs.webkit.org/show_bug.cgi?id=66986
Summary [chromium] Crash on screen unlock on XP due to cycle in layer tree
Iain Merrick
Reported 2011-08-25 15:10:44 PDT
[chromium] Crash on screen unlock on XP due to cycle in layer tree
Attachments
Patch (2.34 KB, patch)
2011-08-25 15:14 PDT, Iain Merrick 		no flags
DetailsFormatted DiffDiff
Patch (2.37 KB, patch)
2011-08-25 15:20 PDT, Iain Merrick 		no flags
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
Iain Merrick
Comment 1 2011-08-25 15:14:00 PDT
Created attachment 105257 [details] Patch
WebKit Review Bot
Comment 2 2011-08-25 15:15:53 PDT
Attachment 105257 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/WebCore/ChangeLog', u'Source/WebCor..." exit_code: 1 Source/WebCore/ChangeLog:6: Line contains tab character. [whitespace/tab] [5] Source/WebCore/ChangeLog:7: Line contains tab character. [whitespace/tab] [5] Source/WebCore/ChangeLog:8: Line contains tab character. [whitespace/tab] [5] Source/WebCore/ChangeLog:9: Line contains tab character. [whitespace/tab] [5] Total errors found: 4 in 3 files If any of these errors are false positives, please file a bug against check-webkit-style.
Iain Merrick
Comment 3 2011-08-25 15:20:30 PDT
Created attachment 105258 [details] Patch
Iain Merrick
Comment 4 2011-08-25 15:26:07 PDT
See discussion on http://code.google.com/p/chromium/issues/detail?id=93761 Looks like the tree corruption *is* fixed, but we were still testing on an older revision on XP. Closing off this patch (but if this issue crops up again, it may still be useful).
Eric Seidel (no email)
Comment 5 2011-09-06 15:42:46 PDT
Comment on attachment 105258 [details] Patch Cleared review? from attachment 105258 [details] so that this bug does not appear in http://webkit.org/pending-review. If you would like this patch reviewed, please attach it to a new bug (or re-open this bug before marking it for review again).
Note You need to log in before you can comment on or make changes to this bug.