Comment #20 on issue 28547 by [email protected]: Chrome causing -10810 errors? http://code.google.com/p/chromium/issues/detail?id=28547
Additional testing procedures: I suggest the following stress test. In addition to doing simple page loads and checking the counts, also load complex pages and close the tab while the page is still loading. Do this at various stages during loading, but especially at fairly late stages in loading (when many things have rendered, but not everything has loaded). I found this to cause leaks which my previous patch did not fix. Remember that the all-important counts are the one before starting the browser and after quitting. Also, a slightly better command to use (instead of the simple "launchctl bslist | wc -l") is: launchctl bslist | grep 'com\.Breakpad\.Inspector' | wc -l (this reduces the chances of other things "contaminating" the count). -- 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
