Closed
Bug 967166
Opened 10 years ago
Closed 10 years ago
MozStumbler: Quit doesn't quit
Categories
(Cloud Services :: Server: Location, defect)
Cloud Services
Server: Location
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rex, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release) Build ID: 20131205075310 Steps to reproduce: Start MozStumber, gather some data, quit the application (menu, quit) Actual results: When restarting the application, the current stats (Reports sent, Wi-Fi access points scanned, etc.) contain the counters and values from prior to the quit. If I reboot the phone or "force quit" the application, these counters are reset. Expected results: After quitting, the MozStumbler process should stop and all the counters should reset. Starting the application after a quit should be the same as starting the application after a phone restart.
Reporter | ||
Comment 1•10 years ago
|
||
Note that after "quitting" the ScannerService is still in the process list and is consuming CPU (and battery)
Reporter | ||
Updated•10 years ago
|
Component: General → Location
Reporter | ||
Comment 2•10 years ago
|
||
I noticed the comment on another bug requesting posting MozStumber issues to github. This has been done at: https://github.com/mozilla/MozStumbler/issues/385
Comment 3•10 years ago
|
||
Moved to github, closing here.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•