gabriel-cardoso
commented
11 years ago Tough one... need to investigate if it comes from the Web Audio API which
has a current_time variable running up and up or from ShareJS using a web
socket always open.
A good solution would be to have a "go to sleep" fonctionnality (Grooveshark or Hootsuite alike) shutting down the app after 1 hour with of inactivity.
-- Gabriel Cardoso
- 12 rue de Domrémy, 75013 Paris, France*
- +336 89 07 24 98*
- gcardoso.w *
- http://twitter.com/amesons http://www.linkedin.com/in/gcardosow http://geekli.st/gc http://github.com/gabriel-cardoso*
2013/7/17 Richard notifications@github.com
When having tabs open in your browser and leaving them open for a longer period of time (like overnight) they lock themselves and your are unable to go to them. Closing this will probably resolve this but I wonder if there are processes that might loop till the application crashes after x amount of time.
— Reply to this email directly or view it on GitHubhttps://github.com/gabriel-cardoso/clawlab-issues/issues/15 .
richardj
When having tabs open in your browser and leaving them open for a longer period of time (like overnight) they lock themselves and your are unable to go to them. Closing this will probably resolve this but I wonder if there are processes that might loop till the application crashes after x amount of time.