356591 - Redirect or compressed content causing lockup.

Status: RESOLVED WONTFIX

(Core :: Networking, defect)

Description

[nbates]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

This url locks up the browser:  http://washingtonpost.com/sitemap.xml.gz
and is a redirect to: http://www.washingtonpost.com/sitemap.xml.gz

This is a small file, 398K.

I've had mixed results on a few pcs with loading the latter.  I can't verify, but one machine properly dl'd http://www.washingtonpost.com/sitemap.xml.gz.

Lynx returns:

[batesn@localhost batesn]$ curl -vvv -O washingtonpost.com/sitemap.xml.gz
* About to connect() to washingtonpost.com port 80
*   Trying 12.129.147.65... connected
* Connected to washingtonpost.com (12.129.147.65) port 80
> GET /sitemap.xml.gz HTTP/1.1
> User-Agent: curl/7.15.1 (sparc-sun-solaris2.9) libcurl/7.15.1 OpenSSL/0.9.7c zlib/1.1.4
> Host: washingtonpost.com
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Server: "webserver"
< Date: Fri, 13 Oct 2006 16:45:48 GMT
< Content-length: 0
< Content-type: text/html
< Location: http://www.washingtonpost.com/sitemap.xml.gz

versus:

[batesn@localhost batesn]$ curl -vvv -O http://www.washingtonpost.com/sitemap.xml.gz
* About to connect() to www.washingtonpost.com port 80
*   Trying 12.129.147.65... connected
* Connected to www.washingtonpost.com (12.129.147.65) port 80
> GET /sitemap.xml.gz HTTP/1.1
> User-Agent: curl/7.15.1 (sparc-sun-solaris2.9) libcurl/7.15.1 OpenSSL/0.9.7c zlib/1.1.4
> Host: www.washingtonpost.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: "webserver"
< Date: Fri, 13 Oct 2006 17:31:56 GMT
< Content-length: 398445
< Content-type: text/xml
< Content-encoding: x-gzip
< Last-modified: Mon, 11 Sep 2006 07:31:21 GMT
< Etag: "6146d-450510c9"
< Accept-ranges: bytes

I searched for:
  redirect compressed xml (and most 2 and 3 word permutations)

Reproducible: Always

Steps to Reproduce:
1. Going to http://washingtonpost.com/sitemap.xml.gz causes lockup.
2. Going to http://www.washingtonpost.com/sitemap.xml.gz cause lockup most times (if not all).

Actual Results:  
Browser locked up.

Expected Results:  
Displayed the redirected xml document.

Comment 1

[Radek 'sysKin' Czyz]

I didn't get a permanent lock-up but there was a 20-second "not responding" period of 100% cpu usage during which memory usage rose to over a gigabyte.

It then showed a large xml tree.

When I went back and opened the file again, memory usage kept rising and unfortunately hit the process' 2 GiB limit, leading to bp-2c5fbaa4-84f8-4e63-af44-d8edf2081221

If I closed the tab and waited a bit, memory usage would drop back. So it wasn't a leak, just very large usage.

Can it be that the document - when uncompressed - is simply insanely large?

Comment 2

[Artem S. Tashkinov]

The current unpacked version of this document weighs 8'610'405 bytes but there's still something terribly wrong with Firefox because at the time this document is being loaded you cannot do anything else with your browser - it completely locks up for me for around thirty seconds.

Comment 3

[Jim Jeffery not reading bug-mail 1/2/11]

crashes for me also using latest hourly, Marking as New:

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20081221 Minefield/3.2a1pre Firefox/3.0.4 ID:20081221111445

Comment 4

[hhh]

Wow, still a hard crash on http://washingtonpost.com/sitemap.xml.gz 

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090715 Minefield/3.6a1pre

Comment 5

[Benjamin Smedberg]

The crash is a OOM exception, not exploitable and not a blocker.