Closed
Bug 735114
Opened 14 years ago
Closed 13 years ago
crash in mozilla::hal::NotifyBatteryChange
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: nhirata, Unassigned)
References
Details
(Keywords: crash, testcase, Whiteboard: [mobile-crash][native-crash])
Crash Data
Attachments
(1 file)
|
1.12 KB,
text/html
|
Details |
This bug was filed from the Socorro interface and is
report bp-9334b1a8-c81b-4dab-8274-195032120311 .
=============================================================
Crashing Thread
Frame Module Signature Source
0 libxul.so mozilla::hal::NotifyBatteryChange
1 libxul.so libxul.so@0x8d98e9
2 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:660
3 libxul.so NS_ProcessNextEvent_P obj-firefox/xpcom/build/nsThreadUtils.cpp:245
4 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:110
5 libxul.so MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:208
6 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:201
7 libxul.so nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:189
8 libxul.so nsAppStartup::Run toolkit/components/startup/nsAppStartup.cpp:220
9 libxul.so XRE_main toolkit/xre/nsAppRunner.cpp:3519
10 libxul.so Java_org_mozilla_gecko_GeckoAppShell_nativeRun toolkit/xre/nsAndroidStartup.cpp:103
11 libmozglue.so loadLibs mozglue/android/APKOpen.cpp:724
More Reports:
https://crash-stats.mozilla.com/report/list?version=Fennec%3A11.0b5&query_search=signature&query_type=contains&reason_type=contains&date=2012-03-12&range_value=28&range_unit=days&hang_type=any&process_type=any&signature=mozilla%3A%3Ahal%3A%3ANotifyBatteryChange
reports show from build 20120228204920
|
||
Updated•14 years ago
|
Hardware: All → ARM
|
||
Comment 1•13 years ago
|
||
I'm seeing this crash with this testcase.
The iframe content is this:
<html>
<head>
<script>
var mozbatt = window.navigator.battery || window.navigator.mozBattery || window.navigator.webkitBattery;
function doe() {
for (var i=0;i<100;i++) {
mozbatt.addEventListener("chargingchange", function() {}, true);
var evt = document.createEvent('CustomEvent');
evt.initCustomEvent('chargingchange', true, true, null);
mozbatt.dispatchEvent(evt);
}
}
setInterval(doe, 10);
</script>
</head>
</html>
https://crash-stats.mozilla.com/report/index/bp-6c06fad9-7f54-4e95-9414-647032120516
|
|
||
Updated•13 years ago
|
|
|
||
Updated•13 years ago
|
blocking-fennec1.0: --- → ?
Component: General → DOM
Product: Fennec → Core
QA Contact: general → general
Whiteboard: [mobile-crash] → [mobile-crash][native-crash]
|
|
||
Updated•13 years ago
|
tracking-fennec: --- → 15+
blocking-fennec1.0: ? → -
|
|
||
Updated•13 years ago
|
Summary: crash [mozilla::hal::NotifyBatteryChange] → crash in mozilla::hal::NotifyBatteryChange
|
||
Comment 2•13 years ago
|
||
I'm not very good at using crash-stats but I can't see any instance of that crash since the 2012
-03-03. Also, I tried the testcase on my phone using a Nightly and everything went fine.
|
|
||
Comment 3•13 years ago
|
||
Yeah, the testcase doesn't seem to crash anymore.
|
|
||
Comment 4•13 years ago
|
||
The latest crashes happened in 15.0a1/20120524 and 14.0b3.
|
|
||
Comment 5•13 years ago
|
||
(In reply to Scoobidiver from comment #4)
> The latest crashes happened in 15.0a1/20120524 and 14.0b3.
Sounds like we can resolve this bug in some manner - Naoki, do you agree?
|
|
Reporter | |
Comment 6•13 years ago
|
||
If the test case doesn't crash any more... and there's no recent crashes, most likely yes.
|
|
||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
|
Assignee | |
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•