Re: Threading Bug Causing Corrupted File Response

[Sunny Hirai <thesunny@gmail.com>]

Oops, sorry. It is not Builder. I can get the errors for it after all.

Sunny

On Jan 25, 7:53 pm, Sunny Hirai <thesu...@gmail.com> wrote:
> Okay, narrowed it down a little. It only happens with Rack::Builder.
>
> Actually, the error is hard to reproduce when going directly to the
> web service because everything happens fast. We put in a proxy to
> simulate slow connections and that's what is causing the problems to
> show up more.
>
> Sunny
>
> On Jan 25, 7:44 pm, Sunny Hirai <thesu...@gmail.com> wrote:
>
> > There appears to be a threading related bug where if you try and load
> > the same file twice at the same time, you get an error that flashes in
> > Firefox before displaying the image that says:
>
> >   The image "path/to/image.png" cannot be displayed, because it
> > contains errors.
>
> > Since this was working before, I'm guessing the bug was introduced in
> > 1.1 or at least a recent-ish release (not exactly sure when the bug
> > crawled in).
>
> > Although I was using a custom file mapper, this bug still happens in
> > Rack's file mapper. I can replicate by doing:
>
> > app = Rack::Builder.new do
> >   run Rack::File.new( '.' )
> > end
>
> > If I hit the file twice quickly, Firefox will flash the error. It will
> > retry immediately so the image eventually comes up but there are twice
> > as many requests made.
>
> > The bug can be replicated using both Mongrel and WEBrick.
>
> > Sunny Hirai
>
>