765678 - startup crash in sqlite3_os_end

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect)

Description

[Scoobidiver (away)]

It's #26 top crasher in 14.0b7.

Signature 	sqlite3_os_end More Reports Search
UUID	9c0fa2c1-e539-4867-b1f2-f4faa2120618
Date Processed	2012-06-18 07:26:03
Uptime	1
Install Age	1.6 days since version was first installed.
Install Time	2012-06-16 16:27:17
Product	FennecAndroid
Version	14.0
Build ID	20120614153549
Release Channel	beta
OS	Linux
OS Version	0.0.0 Linux 2.6.35.7-I9100XWKI4-CL575468 #2 SMP PREEMPT Wed Sep 14 20:49:18 KST 2011 armv7l
Build Architecture	arm
Build Architecture Info	
Crash Reason	SIGSEGV
Crash Address	0x36a860
App Notes 	
AdapterVendorID: smdkc210, AdapterDeviceID: GT-I9100.
AdapterDescription: 'Model: 'GT-I9100', Product: 'GT-I9100', Manufacturer: 'samsung', Hardware: 'smdkc210''.
samsung GT-I9100
samsung/GT-I9100/GT-I9100:2.3.4/GINGERBREAD/XWKI4:user/release-keys
EMCheckCompatibility	True

Frame 	Module 	Signature 	Source
0 	libsqlite.so 	sqlite3_os_end 	
1 	libsqlite.so 	sqlite3_malloc 	
2 	libsqlite.so 	sqlite3_db_config 	
3 	libsqlite.so 	sqlite3_test_control 	
4 	libsqlite.so 	sqlite3_test_control 	
5 	libsqlite.so 	sqlite3_test_control 	
6 	libsqlite.so 	sqlite3_test_control 	
7 	libsqlite.so 	sqlite3_result_null 	
8 	libsqlite.so 	sqlite3_result_null 	
9 	libsqlite.so 	sqlite3_blob_open

More reports at:
https://crash-stats.mozilla.com/report/list?signature=sqlite3_os_end

Comment 1

[Kevin Brosnan [Ex-Mozilla]]

Is this Mozilla sqlite or Android?

Comment 2

[D. Richard Hipp]

The sqlite3_test_control() function is used for testing only.  FF never uses it.  And it is not recursive.  Nor is sqlite3_result_null() recursive.  These facts make me suspect that the stack trace in the bug report is wrong.

Comment 3

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Different crash stack : 
https://crash-stats.mozilla.com/report/index/8c8bbbed-df43-4899-9f54-2e4872120616

Crashing Thread
Frame 	Module 	Signature 	Source
0 	libsqlite.so 	sqlite3_os_end 	
1 	libsqlite.so 	sqlite3_release_memory 	
2 	libsqlite.so 	sqlite3_release_memory 	
3 	libsqlite.so 	sqlite3_db_config 	
4 	libsqlite.so 	sqlite3_db_config 	
5 	libsqlite.so 	sqlite3_reset 	
6 	libsqlite.so 	sqlite3_reset 	
7 	libsqlite.so 	sqlite3_blob_open 	
8 		@0xb848e 	
9 	libsqlite.so 	sqlite3_step 	
10 	libandroid_runtime.so 	libandroid_runtime.so@0x478df 	
11 	dalvik-heap (deleted) 	dalvik-heap @0x4f8fa19 	
12 	dalvik-heap (deleted) 	dalvik-heap @0x8793d6 	
13 	libdvm.so 	dvmPlatformInvoke 	
14 		@0x4014edb2 	
15 	dalvik-LinearAlloc (deleted) 	dalvik-LinearAlloc @0x74956 	
16 	libdvm.so 	dvmCallJNIMethod_general 	
17 	libdvm.so 	dvmAsmSisterStart 	
18 	libdvm.so 	dvmMterpStd 	
19 	libdvm.so 	dvmInterpret 	
20 	libdvm.so 	dvmCallMethodV 	
21 	libdvm.so 	dvmCallMethod 	
22 	libdvm.so 	dvmAttachCurrentThread 	
23 	libc.so 	__thread_entry 	
24 	libc.so 	pthread_create

URLs seen:
about:blank
about:home
http://mafreebox.freebox.fr/download.php

Comment 4

[Gian-Carlo Pascutto [:gcp]]

Maybe related to bug 730495 / bug 721784? I'm asking because sqlite3_os_end + memory functions + sqlite3_db_config in those traces.

Comment 5

[D. Richard Hipp]

Once again, this stack trace does not appear to make sense.  Or perhaps I am not understanding the limitations of these stack traces....

Only applications invoke sqlite3_blob_open().  Some applications, anyway - FF never calls sqlite3_blob_open().  And sqlite3_blob_open() is never called internally by SQLite, and certainly not from sqlite3_step().

sqlite3_blob_open() never calls sqlite3_reset().  And sqlite3_reset() is not recursive - it never calls itself.  And sqlite3_reset() certainly never calls sqlite3_db_config() - that would be crazy.  And sqlite3_db_config() is not recursive, and it never calls sqlite3_release_memory().  The sqlite3_os_end() function is only called from sqlite3_shutdown(), not from sqlite3_release_memory().

It seems like the symbols in the stack trace above are all wrong.  I don't know that the trace is useful in any way.  Either that or I'm not understanding something - perhaps somebody can better explain to me how to interpret these stack traces.

Comment 6

[Wayne Mery (:wsmwk)]

no crashes newer than version 19.0.2 bp-e922af6f-affa-45a5-9290-57b2f2131120