Comment #2 on issue 24842 by bugdro...@chromium.org: We shouldn't be using
NSBundle when we're not sure of thread safety
http://code.google.com/p/chromium/issues/detail?id=24842
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=29077
------------------------------------------------------------------------
r29077 | m...@chromium.org | 2009-10-14 18:22:51 -0700 (Wed, 14 Oct 2009) |
5 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/base_paths_mac.mm?r1=29077&r2=29076
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_paths_internal.h?r1=29077&r2=29076
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_paths_mac.mm?r1=29077&r2=29076
Don't use NSBundle when unsure of thread safety.
BUG=24842
TEST=unit tests pass, app still works
Review URL: http://codereview.chromium.org/271094
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
