Closed
Bug 645714
Opened 14 years ago
Closed 12 years ago
Crash in mozilla::TimeStamp::Now @ PR_Lock
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
mozilla13
People
(Reporter: scoobidiver, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [mobile-crash], str-wanted)
Crash Data
It is #21 top crasher in 4.0. There are two kinds of stack traces: Frame Module Signature [Expand] Source 0 libnspr4.so PR_Lock nsprpub/pr/src/pthreads/ptsynch.c:216 1 libxul.so mozilla::TimeStamp::Now xpcom/ds/TimeStamp.cpp:115 2 libxul.so TimerThread::Run nsTArray.h:139 3 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:633 4 libxul.so NS_ProcessNextEvent_P nsThreadUtils.cpp:250 5 libxul.so nsThread::ThreadFunc xpcom/threads/nsThread.h:85 6 libnspr4.so _pt_root nsprpub/pr/src/pthreads/ptthread.c:190 7 libc.so libc.so@0xfd97 8 libc.so libc.so@0xf863 Frame Module Signature [Expand] Source 0 libnspr4.so PR_Lock nsprpub/pr/src/pthreads/ptsynch.c:216 1 libxul.so mozilla::TimeStamp::Now xpcom/ds/TimeStamp.cpp:115 2 libxul.so nsTimerImpl::SetDelayInternal TimeStamp.h:195 3 libxul.so nsTimerImpl::InitCommon xpcom/threads/nsTimerImpl.cpp:231 4 libxul.so nsTimerImpl::InitWithFuncCallback xpcom/threads/nsTimerImpl.cpp:247 5 libxul.so mozilla::scache::StartupCache::ResetStartupWriteTimer startupcache/StartupCache.cpp:468 6 libxul.so mozilla::scache::StartupCache::PutBuffer startupcache/StartupCache.cpp:287 7 libxul.so mozJSComponentLoader::WriteScript js/src/xpconnect/loader/mozJSComponentLoader.cpp:940 8 libxul.so mozJSComponentLoader::GlobalForLocation js/src/xpconnect/loader/mozJSComponentLoader.cpp:1228 9 libxul.so mozJSComponentLoader::LoadModuleImpl js/src/xpconnect/loader/mozJSComponentLoader.cpp:697 10 libxul.so mozJSComponentLoader::LoadModuleFromJAR js/src/xpconnect/loader/mozJSComponentLoader.cpp:661 11 libxul.so nsComponentManagerImpl::KnownModule::Load xpcom/components/nsComponentManager.cpp:962 12 libxul.so nsFactoryEntry::GetFactory xpcom/components/nsComponentManager.cpp:1948 13 libxul.so nsComponentManagerImpl::CreateInstanceByContractID xpcom/components/nsComponentManager.cpp:1323 14 libxul.so nsComponentManagerImpl::GetServiceByContractID xpcom/components/nsComponentManager.cpp:1676 15 libxul.so CallGetService nsComponentManagerUtils.cpp:95 16 libxul.so nsGetServiceByContractID::operator nsComponentManagerUtils.cpp:279 ... More reports at: https://crash-stats.mozilla.com/report/list?product=Fennec&range_value=4&range_unit=weeks&signature=PR_Lock
Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ PR_Lock ]
On various devices, most current crash report comes from Droid Bionic: https://crash-stats.mozilla.com/report/index/ad8115b5-d218-4a9a-9ef2-243892110913
![]() |
||
Updated•13 years ago
|
Whiteboard: [mobile-crash]
More Signatures: https://crash-stats.mozilla.com/report/list?range_value=7&range_unit=days&date=2011-10-31%2010%3A00%3A00&signature=PR_Lock&version=Fennec%3A10.0a1
Also occurs in native fennec: https://crash-stats.mozilla.com/report/index/6fab3249-781e-4137-968a-d13eb2111105
Whiteboard: [mobile-crash] → [mobile-crash][native-crash]
![]() |
||
Updated•13 years ago
|
Whiteboard: [mobile-crash][native-crash] → [mobile-crash][native-crash:P3]
Marking as P3 : bug has existed in XUL, firefox, need str
Whiteboard: [mobile-crash][native-crash:P3] → [mobile-crash][native-crash:P3], str-wanted
Still occurring; happens in native nightly/aurora : https://crash-stats.mozilla.com/report/list?product=FennecAndroid&query_search=signature&query_type=contains&query=PR_Lock&reason_type=contains&date=01%2F18%2F2012%2015%3A39%3A48&range_value=30&range_unit=days&hang_type=any&process_type=any&do_query=1&admin=1&signature=PR_Lock
status-firefox11:
--- → affected
status-firefox12:
--- → affected
Reporter | ||
Comment 6•13 years ago
|
||
Stacks are more various than the two ones in comment 0. The fix of bug 716345 would help to divide it in several sub-bugs.
Summary: Crash in mozilla::TimeStamp::Now [@ PR_Lock ] mainly close to startup → Crash in mozilla::TimeStamp::Now [@ PR_Lock ]
Comment 6 is correct. There are varying crash stacks in here: https://crash-stats.mozilla.com/report/list?product=FennecAndroid&query_search=signature&query_type=contains&query=PR_Lock&reason_type=contains&date=02%2F09%2F2012%2011%3A28%3A38&range_value=30&range_unit=days&hang_type=any&process_type=any&do_query=1&admin=1&signature=PR_Lock
Happens in both XUL/Native https://crash-stats.mozilla.com/report/list?product=Fennec&product=FennecAndroid&query_search=signature&query_type=contains&query=PR_Lock&reason_type=contains&date=02%2F29%2F2012%2000%3A05%3A58&range_value=30&range_unit=days&hang_type=any&process_type=any&do_query=1&admin=1&signature=PR_Lock Haven't seen it for 13? Not sure if the changes due to timestamp to uptime made a difference?
Reporter | ||
Updated•12 years ago
|
Crash Signature: [@ PR_Lock ] → [@ PR_Lock ]
[@ PR_Lock | mozilla::TimeStamp::Now]
Summary: Crash in mozilla::TimeStamp::Now [@ PR_Lock ] → Crash in mozilla::TimeStamp::Now @ PR_Lock
Comment 9•12 years ago
|
||
We no longer use the NSPR TimeStamp implementation so this should be fixed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•12 years ago
|
Whiteboard: [mobile-crash][native-crash:P3], str-wanted → [mobile-crash], str-wanted
Target Milestone: --- → mozilla13
You need to log in
before you can comment on or make changes to this bug.
Description
•