diff options
| author | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-22 23:47:44 +0000 |
|---|---|---|
| committer | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-22 23:47:44 +0000 |
| commit | a701e5ad76729b657a80d5f4c0c4395a00b94d23 (patch) | |
| tree | 381cf7f466f35c8c5c396f0430ffcb2e9d096c2d /sandbox/src/interception.cc | |
| parent | 7357497e61bbbaa6c55de4070e03e0bcac74a852 (diff) | |
| download | chromium_src-a701e5ad76729b657a80d5f4c0c4395a00b94d23.zip chromium_src-a701e5ad76729b657a80d5f4c0c4395a00b94d23.tar.gz chromium_src-a701e5ad76729b657a80d5f4c0c4395a00b94d23.tar.bz2 | |
Potential fix for the PluginChannel::CleanUp crash. This will go out on tomorrow's dev channel build and we can see if the crashes go away while I try to write a repro.
The only scenario that I can think of is that an NPObject in the plugin process has a deallocate function which releases an npobject from the renderer. That would cause the corresponding NPObjectProxy to go away, but since PluginChannel has in_remove_route_ set, the list won't get updated and in the future iteration of the loop we'll call the method on a deleted object.
BUG=25439
Review URL: http://codereview.chromium.org/327003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29839 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sandbox/src/interception.cc')
0 files changed, 0 insertions, 0 deletions