diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-11 18:44:35 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-11 18:44:35 +0000 |
| commit | 5222bb1495ef2e9a6294da8a8f1b9c1dae2e54e4 (patch) | |
| tree | cd4df5b34e92c7a195f9327f033f761a443841bf /o3d/gpu/np_utils/np_class_unittest.cc | |
| parent | fbb0c1be35b4ab04ad8cd444349c98b1e72fad1c (diff) | |
| download | chromium_src-5222bb1495ef2e9a6294da8a8f1b9c1dae2e54e4.zip chromium_src-5222bb1495ef2e9a6294da8a8f1b9c1dae2e54e4.tar.gz chromium_src-5222bb1495ef2e9a6294da8a8f1b9c1dae2e54e4.tar.bz2 | |
This CL fixes the following issues:-
1. http://code.google.com/p/chromium/issues/detail?id=27200
This was a crash which would occur in the Stop function in the UrlmonUrlRequest object
which would get invoked when the active document instance was being destroyed. The crash
occured if the active document instance was reused in which case we end up reusing the
automation client instance. The fix is to ensure that we clean up existing requests from
the map before reusing the automation client instance.
2. http://code.google.com/p/chromium/issues/detail?id=27202
This was a DCHECK which would occur when adding a new request to the request map, which
indicated that an existing request with the same request id existed in the map. This would
occur during a redirect where the request id is reused by Chrome. Fix is to remove the
request from the map when we handle the AutomationMsg_RequestEnd message in the UI thread
itself. The UrlmonUrlRequest functions which attempt to remove the request from the map
now check if the request is valid before doing this.
Bug=27200,27202
Review URL: http://codereview.chromium.org/388008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31681 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'o3d/gpu/np_utils/np_class_unittest.cc')
0 files changed, 0 insertions, 0 deletions