559456 - Crash in [@ fts3ColumnMethod ][@ @0x656c6261]

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: Silverlight (Microsoft), defect)

Description

[Marcia Knous [:marcia]]

Seen while running  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100413 Firefox/3.6.4 Glue/4.5 (.NET CLR 3.5.30729)

STR:
1. Unsure. Doing exploratory testing of OOPP on Windows XP. Had many tabs open with Flash, Quicktime and Silverlight content.
2. At the time of the crash I think I might have been on http://collections.tepapa.govt.nz/exhibitions/pounamu/PounamuWall.aspx or opening it from another link. I crashed right after that.

https://crash-stats.mozilla.com/report/index/a7fea367-8091-42ab-9ac4-4abbd2100414

Comment 1

[Marcia Knous [:marcia]]

Maybe something to do with Silverlight application storage? When I right click on the content in the url I see two sites are storing application content: http://www.preraphaelites.org and tweetdone.com.

Comment 2

[timeless]

So nss uses sqlite too

Signature	fts3ColumnMethod
UUID	a7fea367-8091-42ab-9ac4-4abbd2100414
Time 	2010-04-14 15:56:38.47605
Uptime	4776
Last Crash	12603 seconds before submission
Product	Firefox
Version	3.6.4
Build ID	20100413172113
OS	Windows NT
OS Version	5.1.2600 Service Pack 3
CPU	x86
CPU Info	GenuineIntel family 15 model 6 stepping 4
Crash Reason	EXCEPTION_ACCESS_VIOLATION
Crash Address	0x656c6261
User Comments	Crashed while several tabs were open including a silverlight site
Processor Notes 	
Related Bugs

Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 		@0x656c6261 	
1 		@0x12f9ff 	
2 	sqlite3.dll 	fts3ColumnMethod 	db/sqlite3/src/sqlite3.c:100379
3 	ssl3.dll 	ssl3.dll@0x6f 	
4 	xul.dll 	nsCOMPtr<nsIByteRangeRequest>::nsCOMPtr<nsIByteRangeRequest> 	obj-firefox/dist/include/nsCOMPtr.h:573
5 	xul.dll 	nsPluginStreamListenerPeer::OnDataAvailable 	modules/plugin/base/src/nsPluginHost.cpp:1967
6 	xul.dll 	NS_TableDrivenQI 	obj-firefox/xpcom/build/nsISupportsImpl.cpp:49
7 	xul.dll 	nsStreamListenerTee::OnDataAvailable 	netwerk/base/src/nsStreamListenerTee.cpp:108
8 	xul.dll 	nsHttpChannel::OnDataAvailable 	netwerk/protocol/http/src/nsHttpChannel.cpp:5388
9 	xul.dll 	nsInputStreamPump::OnStateTransfer 	netwerk/base/src/nsInputStreamPump.cpp:508
10 	mozcrt19.dll 	free 	obj-firefox/memory/jemalloc/crtsrc/jemalloc.c:6017
11 	xul.dll 	nsInputStreamPump::OnInputStreamReady 	netwerk/base/src/nsInputStreamPump.cpp:398
12 	xul.dll 	nsInputStreamReadyEvent::Run 	xpcom/io/nsStreamUtils.cpp:191
13 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:527
14 	xul.dll 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:118
15 	xul.dll 	xul.dll@0x9a4307 	
16 	xul.dll 	MessageLoop::RunHandler 	ipc/chromium/src/base/message_loop.cc:199
17 	xul.dll 	nsComponentManagerImpl::GetServiceByContractID 	xpcom/components/nsComponentManager.cpp:2199
18 	xul.dll 	xul.dll@0x307d13 	
19 	xul.dll 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:173
20 	nspr4.dll 	_PR_MD_CLEAN_THREAD 	nsprpub/pr/src/md/windows/w95thred.c:211

Filename 	Version 	Debug Identifier 	Debug Filename
sqlite3.dll 	3.6.22.0 	D4C568C84A304EC78E4D2520AEB268C51 	sqlite3.pdb
ssl3.dll 	3.12.6.2 	EB498F2997BA451FA7E8F172CA8A7AB51 	ssl3.pdb

Comment 3

[Shawn Wilsher :sdwilsh]

Is NSS actually using fts3?

Comment 4

[timeless]

dunno, but based on the stack trace, it's much more likely to be going through nss than places

Comment 5

[Nelson Bolyard (seldom reads bugmail)]

libssl3 makes no calls into sqlite3.

Comment 6

[timeless]

well, libnss3 could call into softoken which does use sqlite3, right?

but the problem with these stack traces is that we have more than one frame without any symbols. so it's all speculation -- including on the part of the stack walker, when it tried to figure out the calling frames.

It's probably better to blame silverlight.

marcia: when you crash, can you try to get .dmp files for your crashes and save them somewhere? sometimes we're able to get .dmp files later, but in this case I can't find a matching crash report in crash-stats, which means we're stuck with what turns out to be an unwieldy paper report :(.

I'm moving this to silverlight and closing it as incomplete.