Closed Bug 514234 Opened 15 years ago Closed 15 years ago

Crash during upgrade Sunbird 0.9 to Sunbird 1.0pre

Categories

(Calendar :: General, defect)

x86
Windows 7
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ssitter, Unassigned)

Details

(Keywords: crash, Whiteboard: [needed beta][no l10n impact])

Crash during upgrade Sunbird 0.9 to Sunbird 1.0pre

Steps To Reproduce:
1. Create new profile using Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.18pre) Gecko/20080917 Sunbird/0.9
2. Open profile using Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.4pre) Gecko/20090902 Calendar/1.0pre

3 crash reports were submitted resulting in 3 different stack traces:

http://crash-stats.mozilla.com/report/index/7c76c3ee-4c80-42da-97f7-f6eee2090902
http://crash-stats.mozilla.com/report/index/cef5e97c-851f-4b35-b790-4fbbe2090902
http://crash-stats.mozilla.com/report/index/e4cc16e6-7702-465d-8e8b-bc70f2090902
If confirmed this should be blocking 1.0!
Flags: blocking-calendar1.0?
1/3 crashes here:
Signature	js_PCToLineNumber
UUID	7c76c3ee-4c80-42da-97f7-f6eee2090902
Time 	2009-09-02 10:33:29.838745
Uptime	3
Last Crash	9749203 seconds before submission
Product	Sunbird
Version	1.0pre
Build ID	20090902050641
Branch	1.9.1
OS	Windows NT
OS Version	6.1.7100
CPU	x86
CPU Info	AuthenticAMD family 16 model 4 stepping 2
Crash Reason	EXCEPTION_ACCESS_VIOLATION
Crash Address	0xfffffffffdddfddc
User Comments	STS Test upgrade from Sunbird 0.9 to 1.0pre
Processor Notes 	
Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	js3250.dll 	js_PCToLineNumber 	js/src/jsscript.cpp:1824
1 	js3250.dll 	PopulateReportBlame 	js/src/jscntxt.cpp:1260

2/3 crashes here:
Signature	RtlpInsertFreeBlock
UUID	e4cc16e6-7702-465d-8e8b-bc70f2090902
bp-cef5e97c-851f-4b35-b790-4fbbe2090902
Time 	2009-09-02 10:44:36.190368
Uptime	1
Last Crash	276 seconds before submission
Product	Sunbird
Version	1.0pre
Build ID	20090902050641
Branch	1.9.1
OS	Windows NT
OS Version	6.1.7100
CPU	x86
CPU Info	AuthenticAMD family 16 model 4 stepping 2
Crash Reason	EXCEPTION_ACCESS_VIOLATION
Crash Address	0xfffffffffcba3db2
User Comments	STS Test upgrade from Sunbird 0.9 to 1.0pre again
Processor Notes 	
Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	ntdll.dll 	RtlpInsertFreeBlock 	
1 	ntdll.dll 	RtlpFreeHeap 	
2 	ntdll.dll 	RtlpFreeHeap 	
3 	kernel32.dll 	HeapFree 	
4 	msvcr80.dll 	free 	
5 	sqlite3.dll 	sqlite3_free 	db/sqlite3/src/sqlite3.c:16436
6 	sqlite3.dll 	freeIndex 	db/sqlite3/src/sqlite3.c:61526
7 	sqlite3.dll 	sqlite3CreateIndex 	db/sqlite3/src/sqlite3.c:63935
8 	sqlite3.dll 	yy_reduce 	db/sqlite3/src/sqlite3.c:85652
9 	sqlite3.dll 	sqlite3Parser 	db/sqlite3/src/sqlite3.c:86024
10 	sqlite3.dll 	sqlite3RunParser 	db/sqlite3/src/sqlite3.c:86826
11 	sqlite3.dll 	sqlite3Prepare 	db/sqlite3/src/sqlite3.c:72148
12 	sqlite3.dll 	sqlite3_exec 	db/sqlite3/src/sqlite3.c:69057
13 	sunbird.exe 	mozStorageConnection::ExecuteSimpleSQL 	storage/src/mozStorageConnection.cpp:372
14 	xpcom_core.dll 	NS_InvokeByIndex_P 	xpcom/reflect/xptcall/src/md/win32/xptcinvoke.cpp:101
15 	sunbird.exe 	XPCWrappedNative::CallMethod 	js/src/xpconnect/src/xpcwrappednative.cpp:2454
16 	sunbird.exe 	XPC_WN_CallMethod 	js/src/xpconnect/src/xpcwrappednativejsops.cpp:1590
Interesting, I wonder what SQL was executed there and if its the actual SQL call thats breaking there or there is another reason?

timeless, do you know any other reason this might have happened?

Setting blocking+, especially since this is happening to a reviewer of a blocking bug ;-)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-calendar1.0? → blocking-calendar1.0+
Whiteboard: [needed beta][no l10n impact]
Stefan, could you debug this and find out what kind of SQL is being called there? I can't reproduce this on linux.
nope :)
Keywords: crash
I'm not able to reproduce this crash anymore. Maybe something in my system changed or maybe something in Sunbird changed.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.