[B2G][Settings][Bluetooth] System crashes when turning OFF Bluetooth

RESOLVED INCOMPLETE

Status

Firefox OS
Bluetooth
RESOLVED INCOMPLETE
5 years ago
5 years ago

People

(Reporter: sarsenyev, Assigned: gyeh)

Tracking

({crash, regression})

unspecified
ARM
Gonk (Firefox OS)
crash, regression

Firefox Tracking Flags

(blocking-b2g:koi+)

Details

(Whiteboard: burirun3, crash signature, URL)

(Reporter)

Description

5 years ago
Description:
When switching OFF "Bluetooth" the phone freezes 

Repro Steps:
1) Updated Buri to BuildID: 20131030004003
2) Open "Settings" from the home screen
3) Navigate into "Bluetooth"
4) Switch "Bluetooth" OFF

Actual:
The device freezes and nonfunctional

Expected:
The "Bluetooth switches ON/OFF without crashing

Device: Buri v1.2 COM RIL
BuildID: 20131030004003
Gaia: a788ea1a3e04716938bd41a559c36a831cf1190b
Gecko: 4fbe1b01ed63
Version: 26.0a2
RIL Version: 01.02.00.019.082 
Firmware Version: US_20131015

Notes:
Repro frequency: 100%
See attached: crash-report link

Updated

5 years ago
blocking-b2g: --- → koi?
Keywords: crash, regression

Updated

5 years ago
Crash Signature: [@ mozilla::detail::RefCounted<mozilla::dom::bluetooth::BluetoothProfileController, (mozilla::detail::RefCountAtomicity)1>::Release() const]
Since it's related to BluetoothProfileController, Gina can take a first look.
Assignee: nobody → gyeh
koi+ based on the actual.
blocking-b2g: koi? → koi+
(Assignee)

Comment 3

5 years ago
Unfortunately, I cannot reproduce it with the same build on buri. Need QA for further verification.
Keywords: qawanted

Updated

5 years ago
QA Contact: mvaughan

Comment 4

5 years ago
Attempted several times to reproduce this issue on the same build from comment 0, but I was not able to get the crash to happen. Additionally, the reporter could no longer reproduce the issue as well. We are thinking it was that we enabled Bluetooth in an earlier build (most likely the 10/25/13 build), updated the Buri to the 10/30/13 build, and then disabled the already active Bluetooth from there which caused the crash... due to there being lingering 10/25/13 settings or what not.
Keywords: qawanted
(In reply to Matthew Vaughan from comment #4)
> Attempted several times to reproduce this issue on the same build from
> comment 0, but I was not able to get the crash to happen. Additionally, the
> reporter could no longer reproduce the issue as well. We are thinking it was
> that we enabled Bluetooth in an earlier build (most likely the 10/25/13
> build), updated the Buri to the 10/30/13 build, and then disabled the
> already active Bluetooth from there which caused the crash... due to there
> being lingering 10/25/13 settings or what not.

Can you try testing an OTA update then from a 10/25 build to a 11/1 build to see if this reproduces then? OTA update testing should be unblocked now.
Keywords: qawanted
(In reply to Jason Smith [:jsmith] from comment #5)
> (In reply to Matthew Vaughan from comment #4)
> > Attempted several times to reproduce this issue on the same build from
> > comment 0, but I was not able to get the crash to happen. Additionally, the
> > reporter could no longer reproduce the issue as well. We are thinking it was
> > that we enabled Bluetooth in an earlier build (most likely the 10/25/13
> > build), updated the Buri to the 10/30/13 build, and then disabled the
> > already active Bluetooth from there which caused the crash... due to there
> > being lingering 10/25/13 settings or what not.
> 
> Can you try testing an OTA update then from a 10/25 build to a 11/1 build to
> see if this reproduces then? OTA update testing should be unblocked now.

The other option you could try is flash a clean 10/25 build, do the STR you are describing, then flash a 11/1 build without removing profile data, and then finish the STR.

Comment 7

5 years ago
I attempted the option from comment 5 by going to a newer 1.2 build from 10/25 using OTA on a Leo (since this device is the one we can use OTA on at this time). Unfortunately the build it updated my device to is the 10/28 build. The Update channel it was working off of is "leo/1.2.0/nightly". With that said, I could not reproduce this bug using this option. 

I could not get this bug to reproduce using the option in comment 6 either. I attempted about 5 times mixing up some profile data and which RIL I put on the device each time.
Keywords: qawanted
Was the phone in question paired to a bluetooth device at the time the crash occurred?
(Reporter)

Comment 9

5 years ago
(In reply to Marcia Knous [:marcia - use needinfo] from comment #8)
> Was the phone in question paired to a bluetooth device at the time the crash
> occurred?

Here is the steps how I was able to see the crash:
Two Buri devices was paired with Bluetooth connection. I tried to share an image for a test, but for some reason the "share" button didn't work, I re-flashed the device, but the "share" button still didn't work. Then I was reset the device and the "share" button is worked.  But after a couple minutes when I tried to reconnect the device, the crash is reproduced for many times.
I was not able to reproduce this issue on other devices and then when I re-flashed the device again the was no longer reproducible
I'm going to put needinfo on Marcia to see if she can investigate comment 9 to see if she can reproduce the original crash.
Flags: needinfo?(mozillamarcia.knous)
I tried reproducing this on Friday using the STR in Comment 9 but I didn't have any luck. The main issue I encountered was having trouble consistently sharing pictures between two Buri devices - but I never hit the crash described.
Flags: needinfo?(mozillamarcia.knous)
Okay. Sounds like we've got nothing actionable here - closing as incomplete. Reopen if someone figures out how to reproduce this again.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.