search

kzahel / web-server-chrome

An HTTP Web Server for Chrome (chrome.sockets API)
https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb
Other
1.24k stars 275 forks source link

Resume after screen lock #181

Open LiverpoolFC opened 5 years ago

LiverpoolFC commented 5 years ago

Server doesn't restart after login from pin lock screen.

Steps: 1) server is running 2) enter screen lock 3) resume next day, PIN fails (timeout?) so log in via password 4) server isn't running 5) toggle start/stop -> server runs fine

Software: Google Chrome OS (Official Build) (64-bit): Version 73.0.3683.114 Web Server for Chrome: Version 0.4.8

Settings: Run in background: ON Start on login: ON Accessible on local network: ON Automatically show index.html: ON All other settings (including advanced settings): OFF

Hardware: Lenovo Chromebox Tiny CPU: Intel Core i3-5005U (2.0 GHz) RAM: 16GB RAM SSD: 256GB

kzahel commented 5 years ago

Interesting. I'm assuming it only occurs after the PIN unlock fails? What about if you use this extension to keep the computer from sleeping? https://chrome.google.com/webstore/detail/keep-awake/bijihlabcfdnabacffofojgmehjdielb

kzahel commented 5 years ago

Just pulled out an old Chromebit and going to see if I can reproduce over next some days

LiverpoolFC commented 5 years ago

NB: checks are made on same device that the server is running on.

I've tried the following: 1) Check after heavy CPU use. 2) Check after timeout. 3) Check after forced lock screen. 4) Check after power cycle.

Unfortunately, I'm getting inconsistent results. Power cycle (case 4) always works. Case 1 is especially strange. Sometimes the server just hangs. The timeout/lockscreen behavior is also inconsistent. Sometimes it works, sometimes not.

It's a royal pain to have software with issues that are hard to reproduce. Believe me, I know. I've been dealing with such things since the days of UNIX Version 7 on a DEC PDP 11/45...