366415 - Ancestry.com sites crash [@ nsXMLHttpRequest::StreamReaderFunc]

Status: RESOLVED WORKSFORME

(Core :: XML, defect, P3)

Description

[Alan Cramer]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061222 Firefox/3.0a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061222 Firefox/3.0a1

When using several features of any Ancestry.com site (eg. ancestry.com, ancestry.co.uk, ancestry.com.au) it causes the browser to close without warning, and the only way to go back is to recover the session.

Reproducible: Always

Steps to Reproduce:
One example of a crash....
1.Goto any ancestry.com site
2.Login to an ancestry.com account
3.Go to My Ancestry
4.Work on a family tree
5.Add a new person
6.While working in fields, browser closes without warning.
Actual Results:  
Mozilla Firefox disappears.

Expected Results:  
Stayed open and allowed me to continue to input data for my Family Tree

Build platform
target
i686-pc-linux-gnu

Build tools
Compiler 	Version 	Compiler flags
i686-pc-linux-gnu-gcc 	gcc version 4.1.1 (Gentoo 4.1.1-r1) 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align -Wno-long-long -march=i686 -pipe -Wno-return-type -w -pthread -pipe
i686-pc-linux-gnu-g++ 	gcc version 4.1.1 (Gentoo 4.1.1-r1) 	-fno-rtti -fno-handle-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -march=i686 -pipe -Wno-return-type -w -fshort-wchar -pthread -pipe -DARON_WAS_HERE

Configure arguments
--enable-application=browser --enable-optimize=-O2 --disable-installer --disable-pedantic --enable-crypto --with-system-jpeg --with-system-png --with-system-zlib --disable-updater --enable-default-toolkit=gtk2 --enable-pango --enable-svg --enable-svg-renderer=cairo --enable-system-cairo --disable-strip --disable-strip-libs --enable-single-profile --disable-profilesharing --disable-profilelocking --enable-ipv6 --disable-xinerama --disable-xprint --disable-freetype2 --disable-debug --disable-tests --enable-reorder --enable-elf-dynstr-gc --enable-application=browser --enable-image-encoder=all --enable-canvas --with-system-nspr --with-system-nss --enable-official-branding --enable-oji --enable-mathml --disable-jsd --disable-xpctools --with-default-mozilla-five-home=/usr/lib/mozilla-firefox --enable-default-toolkit=cairo-gtk2 --disable-system-cairo --enable-extensions=default,typeaheadfind,-venkman --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu

Comment 1

[Alan Cramer]

Similar to Bug 365589 except this is on Linux and with Firefox 3.0a1.  It used to happen on Firefox 2.0 aswell before I upgraded.

Comment 2

[Arie Paap [:wildmyron]]

Confirmed on Windows with the same steps to reproduce. Crash occurs while typing in "Birth Place Field"

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20070108 Minefield/3.0a2pre ID:2007010804 [cairo]

Looking through talkback data this is also occurs for 2.0.0.1 (lots of TBIDs with ancestry.com.* in URL field) nsXMLHttpRequest::StreamReaderFunc is #159 on the topcrasher list for 2.0.0.1

TB28178829Z

Stack Signature	 nsXMLHttpRequest::StreamReaderFunc be3fbac6
Product ID	FirefoxTrunk
Build ID	2007010804
Trigger Time	2007-01-09 05:12:37.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	firefox.exe + (00151fd0)
URL visited	http://www.ancestry.com.au
User Comments	Filling out form
Since Last Crash	155 sec
Total Uptime	155 sec
Trigger Reason	Access violation
Source File, Line No.	e:\builds\tinderbox\fx-trunk\winnt_5.2_depend\mozilla\content\base\src\nsxmlhttprequest.cpp, line 1209
Stack Trace 	
nsXMLHttpRequest::StreamReaderFunc  [mozilla\content\base\src\nsxmlhttprequest.cpp, line 1209]
nsInputStreamTee::WriteSegmentFun  [mozilla\xpcom\io\nsinputstreamtee.cpp, line 103]
nsPipeInputStream::ReadSegments  [mozilla\xpcom\io\nspipe3.cpp, line 764]
nsInputStreamTee::ReadSegments  [mozilla\xpcom\io\nsinputstreamtee.cpp, line 157]
nsXMLHttpRequest::OnDataAvailable  [mozilla\content\base\src\nsxmlhttprequest.cpp, line 1240]
nsStreamListenerTee::OnDataAvailable  [mozilla\netwerk\base\src\nsstreamlistenertee.cpp, line 97]
nsHttpChannel::OnDataAvailable  [mozilla\netwerk\protocol\http\src\nshttpchannel.cpp, line 4117]
nsInputStreamPump::OnStateTransfer  [mozilla\netwerk\base\src\nsinputstreampump.cpp, line 503]
nsInputStreamPump::OnInputStreamReady  [mozilla\netwerk\base\src\nsinputstreampump.cpp, line 394]
nsOutputStreamReadyEvent::Run  [mozilla\xpcom\io\nsstreamutils.cpp, line 112]
NS_ProcessNextEvent_P  [mozilla\xpcom\build\nsthreadutils.cpp, line 225]
nsBaseAppShell::Run  [mozilla\widget\src\xpwidgets\nsbaseappshell.cpp, line 153]
0x003d2ae4
0xccccc3c0

Comment 4

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Peter, got time to look at this one?

Comment 5

[Ryan Jones-Ward [:sciguyryan]]

Does anyone have a reproducible testcase for this?

Comment 6

[Peter Van der Beken [:peterv]]

We really need a reproducible testcase for this one.

Comment 7

[Marye E. Steckley]

Confirmed on Windows with the same steps to reproduce that Alan Cramer detailed.  

Comment 8

[Marye E. Steckley]

What do you need to have to do a reproducible testcase for this?  Let me know what you need me to do to assist you with this Bug.

Comment 9

[Jerry Wear]

Be glad your enhanced viewer did not install into firefox 2.0.0.4. It did on mine and it crashes firefox whenever the viewer starts. I cannot locate the viewer plugin to remove it or identify it in config. I cannot view images on Ancestry.com without this crash problem

Comment 10

[Pavel Penaz]

Did not manage to reproduce on latest trunk build.

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a9pre) Gecko/2007092405 Minefield/3.0a9pre

Comment 11

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Peter, do the steps in comment 0 not work for you?

Comment 12

[Bob Clary [:bc] (inactive)]

Alan, this may be resolved by now. Bug 411531 includes a fix for a different bug I found when trying to test this. I couldn't crash after doing some rather heavy lifting on my ancestry.com trees or when scanning the site. The fix will be available in tomorrow's nightly builds. Will you please try to reproduce a crash tomorrow and report back? Thanks.

Comment 13

[Bob Clary [:bc] (inactive)]

I can not reproduce this crash on linux or windows. Marking works for me. Please reopen if you can reproduce the crash. Thanks.