Closed Bug 905575 Opened 11 years ago Closed 6 years ago

[Buri][Wi-Fi]Turn off Wi-Fi have no effect when memory less than 2MB.

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sync-1, Unassigned)

References

Details

Attachments

(2 files)

30.45 KB, application/x-zip-compressed
Details
136.89 KB, image/x-png
Details
AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.184
 Firefox os  v1.1
 Mozilla build ID:20130806071254
 
 Created an attachment (id=482244)
 Image
 
 DEFECT DESCRIPTION:
 Turn off Wi-Fi have no effect when memory less than 2MB.
 
 REPRODUCING PROCEDURES:
 1)turn on wifi->connected a valid AP->write data to the phone;
 2)pop up "less than 2MB remaining"->switch off the wifi->the wifi show connected still;(refer to the attachment)-->KO
 
 EXPECTED BEHAVIOUR:
 KO:turn on/off wifi is normal.
 
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 Serious
 
 REPRODUCING RATE:
 5/5
 
 For FT PR, Please list reference mobile's behavior:
Clone from brother
Attached file 503038.Logcat log
Clone from brother
Attached image Image
blocking-b2g: --- → koi?
I think indexedDB refuses to store data if we are low on memory.
(In reply to Gregor Wagner [:gwagner] from comment #5)
> I think indexedDB refuses to store data if we are low on memory.

Low on *disk space*.
Any solution will likely be an extra feature, which we will not be able to do at v1.2 timeframe.
blocking-b2g: koi? → 1.3?
Dave,

While do triage this one, we think this is also related memory issue and the solution should be more comprehensive in platform instead of resolving it app by app in system. May I have your comments for changing the component to the correct one. Is it Core->DOM?
Flags: needinfo?(dhylands)
blocking-b2g: 1.3? → 1.4?
(In reply to Ivan Tsay (:ITsay) from comment #8)
> Dave,
> 
> While do triage this one, we think this is also related memory issue and the
> solution should be more comprehensive in platform instead of resolving it
> app by app in system. May I have your comments for changing the component to
> the correct one. Is it Core->DOM?

I think that the real issue is that when memory drops below some critical level (not sure what the exact level is) then all writes to indexed-db fail. Since the settings app uses indexed db, turning off wifi will fail.

It seems to me like the settings app should detect this low-memory condition and post appropriate warnings and/or not allow the user to change the settings until memory is freed up.
Flags: needinfo?(dhylands)
Triage: Need UX team input on the UI behavior to inform user about the disc full. Will address this issue in the future release.
blocking-b2g: 1.4? → ---
Flags: needinfo?(firefoxos-ux-bugzilla)
Flagging Omega on Settings.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(ofeng)
Stephany, just like Bug 903903, I think it should be an issue for the entire system, not just for Settings/Wi-Fi.
Maybe we can to handle this by showing a toast/dialog to inform users or guide them to do something.
Flags: needinfo?(ofeng) → needinfo?(firefoxos-ux-bugzilla)
Flagging Harly to see if this is suitable for BB. We can change the bug component later as required.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(hhsu)
Hi Stephany,
I don't think that this is a pattern which is related to BB. But I would suggest the same thing as Omega has pointed out which we could provide a toast/dialog when system is low on memory.
Flags: needinfo?(hhsu)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: