Updates:
Status: Fixed
Comment #5 on issue 3719 by [email protected]: Shared memory doesn't go
away after crashes and contents can inadventantly get reused in subsequent
runs
http://code.google.com/p/chromium/issues/detail?id=3719
Fixed with the transition to BSD style shmem. Specifically, Chrome uses
anonymous shmem (name=""), which is
unlink()ed after mmap()ing, so it's gone. Tests which use named shmem
specifically delete the shmem before
starting. Also note "locks" are now lockf() which can't be leaked.
--
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
-~----------~----~----~----~------~----~------~--~---
