New issue
Advanced search Search tips

Issue 889455 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 9
Cc:
rsesek@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

log spam around GTMLogMaximumLevelFilter being linked into two places upon startup

Project Member Reported by thakis@chromium.org, Sep 26 
$ /Applications/Google\ Chrome\ Beta.app/Contents/MacOS/Google\ Chrome
objc[12958]: Class GTMLogMaximumLevelFilter is implemented in both /Applications/Google Chrome Beta.app/Contents/Versions/41.0.2272.35/Google Chrome Framework.framework/Google Chrome Framework (0x10a50d0f8) and /Applications/Google Chrome Beta.app/Contents/Versions/41.0.2272.35/Google Chrome Framework.framework/Frameworks/KeystoneRegistration.framework/KeystoneRegistration (0x104cb0bc0). One of the two will be used. Which one is undefined.


I thought this might be due to the linking changes for the new sandbox, but I've seen it in two old (unrelated) years-old bugs (issue 477823, issue 642526) so maybe it's been around for a while.

Comment 1 by rsesek@chromium.org, Sep 26 

It shouldn't be related to the sandbox changes. Seems like it's because both Keystone and Chromium use GTMLogger. I suspect that we'll be able to remove most uses of GTM after Cocoa is gone, so that'll "fix" this.

Comment 2 by a...@chromium.org, Oct 1

Status: Available (was: Untriaged)

Comment 3 by rsesek@chromium.org, Oct 9 

I don't see how this class is being used, since we don't build GTMLogger on Mac. The version above is 41.0.2272.35 - so I think that's the problem.

Comment 4 by thakis@chromium.org, Oct 9

Status: WontFix (was: Available)
I ran `/Applications/Google\ Chrome\ Beta.app/Contents/MacOS/Google\ Chrome` and didn't notice that that opened a window in my running "Google Chrome Dev" process (...which is apparently also running the beta channel? Who set this machine up?)

So yeah, PEBKAC, sorry for the noise.
►

Sign in to add a comment