New issue
Advanced search Search tips

Issue 629619 link

Starred by 3 users
Status: Archived
Owner:
erikc...@chromium.org
Closed: Aug 14
Cc:
a...@chromium.org
rsesek@chromium.org
thakis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Build warnings with Xcode 8 beta 3 from ibtool, doesn’t care for 8bpc/32bpp with gray color space model

Project Member Reported by mark@chromium.org, Jul 19 2016 
I get ten of these warnings from a build with Xcode 8b3 8S174q:

Jul 19 16:06:26  ibtoold[10720] <Error>: CGBitmapContextCreate: unsupported parameter combination: set CGBITMAP_CONTEXT_LOG_ERRORS environmental variable to see the details

So I tried again with that environment variable set:

CGBITMAP_CONTEXT_LOG_ERRORS=1 ninja -C out/debug chrome/app/nibs:chrome_xibs

and got the attached output. The problem shows up in these files (two times in each):

chrome/app/nibs/DevicePermissionsPrompt.xib
chrome/app/nibs/DownloadItem.xib
chrome/app/nibs/ExtensionInstallPrompt.xib
chrome/app/nibs/ExtensionInstallPromptNoWarnings.xib
chrome/app/nibs/ExtensionInstallPromptWebstoreData.xib

An example of the more detailed warning from CGBITMAP_CONTEXT_LOG_ERRORS:

Jul 19 16:16:07  ibtoold[30894] <Error>: 
	CGBitmapContextCreate: unsupported parameter combination:
	 	8 integer bits/component;
	 	32 bits/pixel;
		Gray color space model; kCGImageAlphaPremultipliedLast;
		4 bytes/row.
	Valid parameters for Gray color space model are:
		8  bits per pixel,		 8  bits per component,		 kCGImageAlphaOnly
		8  bits per pixel,		 8  bits per component,		 kCGImageAlphaNone
		8  bits per pixel,		 8  bits per component,		 kCGImageAlphaNoneSkipLast
		8  bits per pixel,		 8  bits per component,		 kCGImageAlphaPremultipliedLast
		16 bits per pixel,		 16 bits per component,		 kCGImageAlphaNone
		16 bits per pixel,		 16 bits per component,		 kCGImageAlphaNone|kCGBitmapFloatComponents
		32 bits per pixel,		 32 bits per component,		 kCGImageAlphaNone|kCGBitmapFloatComponents
	See Quartz 2D Programming Guide (available online) for more information.

It looks like we’re asking for a gray color space model while specifying 8 bits/component and 32 bits/pixel, but this is nonsense for grayscale.

Robert just whacked all of the xibs in  bug 627721  (https://crrev.com/e72747d498e627f937335b584c357925d5c074db, https://codereview.chromium.org/2148373003/). I was expecting the ibtool warnings to go away after that landed, but instead I’m seeing these new warnings. I don’t know if they’re showing up because of something that happened when the xib deployment target changed or something new in Xcode 8b3.
cgbitmap_context_log_errors.txt
18.9 KB View Download

Comment 1 by tapted@chromium.org, Jul 22 2016 

Well.. Extension Install and Device permissions may become obsolete with  Issue 603373 .

DownloadItem will take a while longer. And, even if they become obsolete, it'll probably be a few milestones where we spew out annoying warnings for them.

I'm guessing the DownloadItem one is the little down arrow on the context menu button and we need to replace it with a new image asset to make this warning go away. Currently it's base64-encoded in the .xib. Does the image still appear for a Chrome build that emitted this error?

Comment 2 by mark@chromium.org, Jul 22 2016 

This thing? Yeah, it’s OK.

10.12db3 16A254g
triangle.png
9.8 KB View Download

Comment 3 by tapted@chromium.org, Jul 25 2016

Cc: -erikc...@chromium.org
Owner: erikc...@chromium.org
Status: Assigned (was: Untriaged)
[triage] assigning to get out of the queue.

Another stab-in-the-dark: it's possible opening and re-saving the xibs in a newer XCode could make this go away. But I think that's dependent on  Issue 624049 . So -> erik :)

Anyway, from the anecdotal look at the download button it seems as though nothing falls apart by ignoring these errors [for now..]

Comment 4 by robliao@chromium.org, Aug 14

Status: Archived (was: Assigned)
Archiving old bugs that haven't been modified in over two years. 

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
►

Sign in to add a comment