chromebase OS 49 file persistent kiosk mode
Reported by
supp...@lookingglassnetwork.com,
Mar 22 2016
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. In Kiosk mode, save to file system. 2. turn off 3. turn back on. 4. Keep repeating this process and the file will eventually disappear. What is the expected behavior? File should persist What went wrong? This happens randomly and hard to replicate the problem, although this only happens in Kiosk mode. Please download a file persistent sample app we've created here: https://chrome.google.com/webstore/detail/kiosk-development/ojdhhjifhkcjcocacoepkkfonhaoofll?authuser=0 This same problem seems to stem from my last bug here: https://bugs.chromium.org/p/chromium/issues/detail?id=474605 I want to note that this only affect AOpen ChromeBase All-In-One. All my other ChromeBoxes are fine. Did this work before? N/A Chrome version: 49 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 21.0 r0
,
Mar 28 2016
Also, toURL() does not work when using Volumes. Example:
fs.root.getFile(fileName, {create: false}, function(fileEntry) {
var fileURL = fileEntry.toURL();
console.log("Success");
callback(fileURL);
}, function(){
console.log("Failed");
callback(null);
});
It will always return empty. Please advise.
Note: toURL() works when using HTML5 Filesystem.
,
Mar 29 2016
Juan, please try to reproduce this. Update bug with findings.
,
Apr 4 2016
Issue reproduced. System filed not saved between reboots. System info: CHROMEOS_RELEASE_TRACK=testimage-channel CHROMEOS_RELEASE_DESCRIPTION=7834.58.0 (Official Build) dev-channel sumo test
,
Apr 4 2016
Can you clarify how the issue is repro'd? Which app and what repro steps?
,
Apr 4 2016
Bug reproduced in a Aopen Chromebase (Sumo). App provided:https://chrome.google.com/webstore/detail/kiosk-development/ojdhhjifhkcjcocacoepkkfonhaoofll?authuser=0 Bug is reproducible as OP using the provided App.
,
Apr 4 2016
Is that a device without a battery? And did the problem repro by pulling out the power cord?
,
Apr 4 2016
The problem is reproducible by rebooting by pulling the cord and also by doing a soft reboot
,
Apr 4 2016
Pulling the power cord and losing data is not surprising since M49 still runs with 600s commit interval. And we don't fsync for the app's data file. Soft reboot should not repro though if it is really shuts down cleanly.
,
Apr 25 2016
Is this something that will be looked into further?
,
Apr 25 2016
Things should have improved in M50 after issue 555785 since we decreased commit interval for devices without batteries. Files would have better chance to survive unclean shutdown. We still have not fixed the fs corruption 100% though.
,
Apr 25 2016
Ok I will look forward to the updates.
,
Jul 12 2016
,
Jul 12 2016
,
Jul 21 2016
i am still getting the same issue with 50. Are we still pursuing this issue?
,
Jul 21 2016
Hi Michael, can you please try repro this issue in latest stable? Thanks.
,
Jul 21 2016
Will do!
,
Jul 22 2016
I used an AOpen Chromebase ("sumo") device, with the latest M52-Stable (platform 8350.60.0; chromeos 52.0.2745.85). Installed the persistent file check app, spent a half hour soft-rebooting, and another half hour pulling the plug, and the persistent file didn't disappear.
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by tkent@chromium.org
, Mar 23 2016Labels: -OS-Windows OS-Chrome