|
|
Chromium Code Reviews
Descriptionmac: Tentative fix for Yosemite open file crash.
There's a bug in AppKit that causes Chrome to crash when users attempt to save
or open a file. The code path that causes the crash is only hit by applications
linked against OSX 10.7 SDK (or earlier). This CL registers a default value for
the preference NSViewKeepLayersAround, which prevents this code path from being
hit. The functional implications of changing the preference
NSViewKeepLayersAround are minimal.
BUG=428977
Committed: https://crrev.com/192b9d9cfe388a6cfb76b9aea56070da1d878a81
Cr-Commit-Position: refs/heads/master@{#316968}
Patch Set 1 #Patch Set 2 : Set the default to YES on all OSes. #
Total comments: 2
Patch Set 3 : @(YES) -> @YES #Patch Set 4 : @YES -> @(YES) #Patch Set 5 : Remove trailing comma, just in case. #Messages
Total messages: 24 (8 generated)
erikchen@chromium.org changed reviewers: + andresantoso@chromium.org
Andre: Please review.
On 2015/02/18 22:25:41, erikchen wrote: > Andre: Please review. Andre: PTAL
avi@chromium.org changed reviewers: + avi@chromium.org
https://codereview.chromium.org/941453002/diff/20001/chrome/browser/chrome_br... File chrome/browser/chrome_browser_main_mac.mm (right): https://codereview.chromium.org/941453002/diff/20001/chrome/browser/chrome_br... chrome/browser/chrome_browser_main_mac.mm:269: @"NSViewKeepLayersAround": @(YES), Can you use @YES here?
LGTM
New patchsets have been uploaded after l-g-t-m from andresantoso@chromium.org
On 2015/02/18 22:41:34, Andre wrote: > LGTM LGTM too
https://codereview.chromium.org/941453002/diff/20001/chrome/browser/chrome_br... File chrome/browser/chrome_browser_main_mac.mm (right): https://codereview.chromium.org/941453002/diff/20001/chrome/browser/chrome_br... chrome/browser/chrome_browser_main_mac.mm:269: @"NSViewKeepLayersAround": @(YES), On 2015/02/18 22:40:52, Avi wrote: > Can you use @YES here? Done. There are two instances of @(YES) in the Chrome code base, and no instances of @YES. Looking at the clang documentation (http://clang.llvm.org/docs/ObjectiveCLiterals.html), @YES is more accurate as it uses numberWithBool:. It's unclear what @(YES) gets compiled to.
The CQ bit was checked by erikchen@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/941453002/40001
New patchsets have been uploaded after l-g-t-m from avi@chromium.org
@YES doesn't work, since YES gets preprocessor defined to 1, and @YES becomes @1.
The CQ bit was checked by erikchen@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/941453002/70001
On 2015/02/18 23:57:46, erikchen wrote: > @YES doesn't work, since YES gets preprocessor defined to 1, and @YES becomes > @1. Looks like @YES requires 10.8 or later SDK https://developer.apple.com/library/prerelease/ios/releasenotes/ObjectiveC/Ob...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_rel on tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) Timed out jobs are not retried to avoid causing additional load on the builders with large pending queues.
The CQ bit was checked by erikchen@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/941453002/70001
Message was sent while issue was closed.
Committed patchset #5 (id:70001)
Message was sent while issue was closed.
Patchset 5 (id:??) landed as https://crrev.com/192b9d9cfe388a6cfb76b9aea56070da1d878a81 Cr-Commit-Position: refs/heads/master@{#316968}
Message was sent while issue was closed.
On 2015/02/19 00:02:44, Andre wrote: > On 2015/02/18 23:57:46, erikchen wrote: > > @YES doesn't work, since YES gets preprocessor defined to 1, and @YES becomes > > @1. > > Looks like @YES requires 10.8 or later SDK > https://developer.apple.com/library/prerelease/ios/releasenotes/ObjectiveC/Ob... :( Thanks anyway.
Message was sent while issue was closed.
A revert of this CL (patchset #5 id:70001) has been created in https://codereview.chromium.org/1104733002/ by erikchen@chromium.org. The reason for reverting is: Speculative revert. This CL might be responsible for inverted text in omnibox. https://code.google.com/p/chromium/issues/detail?id=479097. |
