Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(37)

Issue 2787002: Take 2 at working around a multipart crash (Closed)

Created:
10 years, 6 months ago by tony
Modified:
9 years, 7 months ago
Reviewers:
ananta, jam
CC:
chromium-reviews
Base URL:
http://src.chromium.org/git/chromium.git
Visibility:
Public.

Description

Take 2 at working around a multipart crash The work around is to be more aggressive about sending multipart data before we have a response header. We used to buffer a response until we had the full frame. This avoids a crash in webcore by behaving more like CFNetwork. It also makes us behave more like Gecko, which is probably good for compat. The original patch (r47599) broke plugins on Windows because it was depending on the assumption that we would send data as one big chunk. Now that we send data as multiple chunks, we need to update the data offset being sent to the plugin. BUG=30880 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=49355

Patch Set 1 #

Total comments: 1

Patch Set 2 : style #

Unified diffs Side-by-side diffs Delta from patch set Stats (+24 lines, -11 lines) Patch
M webkit/glue/multipart_response_delegate.cc View 1 chunk +12 lines, -0 lines 0 comments Download
M webkit/glue/multipart_response_delegate_unittest.cc View 3 chunks +11 lines, -11 lines 0 comments Download
M webkit/glue/plugins/webplugin_impl.cc View 1 1 chunk +1 line, -0 lines 0 comments Download

Messages

Total messages: 6 (0 generated)
tony
The multipart code was r+ in the original patch by darin. http://codereview.chromium.org/2070007
10 years, 6 months ago (2010-06-09 09:17:05 UTC) #1
jam
lgtm http://codereview.chromium.org/2787002/diff/1/4 File webkit/glue/plugins/webplugin_impl.cc (right): http://codereview.chromium.org/2787002/diff/1/4#newcode112 webkit/glue/plugins/webplugin_impl.cc:112: byte_range_lower_bound_+= data_size; nit missing space
10 years, 6 months ago (2010-06-09 21:21:32 UTC) #2
ananta
LGTM. Please verify that Acrobat reader continues to render byte range optimized PDF files correctly
10 years, 6 months ago (2010-06-09 21:23:55 UTC) #3
tony
On 2010/06/09 21:23:55, ananta wrote: > LGTM. Please verify that Acrobat reader continues to render ...
10 years, 6 months ago (2010-06-10 01:20:56 UTC) #4
iyengar
An example is https://docs.google.com/a/google.com/viewer?url=http://www.bankofengland.co.uk/publications/quarterlybulletin/qb0704.pdf . -Ananta On Wed, Jun 9, 2010 at 6:20 PM, <tony@chromium.org> ...
10 years, 6 months ago (2010-06-10 01:23:09 UTC) #5
tony
10 years, 6 months ago (2010-06-10 02:13:39 UTC) #6
On 2010/06/10 01:23:09, iyengar_google.com wrote:
> An example is
>
https://docs.google.com/a/google.com/viewer?url=http://www.bankofengland.co.u...

You mean without the docs.google.com part, right?  Anyway, it loads for me both
in docs and if I try to load the PDF directly.

Powered by Google App Engine
This is Rietveld 408576698