Index: chrome/common/multi_process_lock_win.cc |
diff --git a/chrome/common/multi_process_lock_win.cc b/chrome/common/multi_process_lock_win.cc |
index ea31da6b19c1504904e905915cce82da7ebe4921..aa24d49f07bd90f878f0aa38771f933659960188 100644 |
--- a/chrome/common/multi_process_lock_win.cc |
+++ b/chrome/common/multi_process_lock_win.cc |
@@ -24,9 +24,9 @@ class MultiProcessLockWin : public MultiProcessLock { |
return true; |
} |
- if (name_.length() > MULTI_PROCESS_LOCK_NAME_MAX_LEN) { |
+ if (name_.length() > MAX_PATH) { |
Mark Mentovai
2011/10/31 15:47:40
Should this be >= to leave room for a 0-terminator
Robert Nagy
2011/11/07 19:23:13
Done.
|
LOG(ERROR) << "Socket name too long (" << name_.length() |
- << " > " << MULTI_PROCESS_LOCK_NAME_MAX_LEN << ") - " << name_; |
+ << " > " << MAX_PATH << ") - " << name_; |
return false; |
} |
cpu_(ooo_6.6-7.5)
2011/10/31 19:26:09
I hope this change does not mean that we are going
Robert Nagy
2011/11/07 19:23:13
MAX_PATH and MULTI_PROCESS_LOCK_NAME_MAX_LEN is ju
|