Comment #6 on issue 21658 by m...@chromium.org: All webpages are painted
white
http://code.google.com/p/chromium/issues/detail?id=21658
Based on the log messages, there's a bad CGBitmapContext due to having a bad
CGColorSpace, and the CG calls that are failing and the order of the
messages points
to skia::BitmapPlatformDevice as the caller
(skia/ext/bitmap_platform_device_mac.cc). The CGBitmapContexts in there are
created using mac_util::GetSystemColorSpace() (base/mac_util.mm), which is
new in
4.0.207.0. (Confirm that this is a regression?)
We "warm up" mac_util::GetSystemColorSpace() during renderer startup before
bringing up the sandbox, but maybe that function is failing for other
reasons.
If you start Chrome with --no-sandbox, does the problem persist?
Can you describe the display configuration a little bit more fully? Color
profiles in
use? Custom calibrations? Displays disconnected and reconnected since
boot?
Could you compile (g++ displays.cc -o displays -framework
ApplicationServices) and
run the attached program, which tries to get some display information? This
program goes through the same motions to get the system profile that
mac_util::GetSystemColorSpace() does in Chrome, and it also tries a few
other things.
(I'd try the test program first, while you're still experiencing problems
in Chrome, so
that you've got a record of it in case checking or playing with any of the
other
settings "fixes" things for you.)
Attachments:
displays.cc 4.9 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
