Just wanted to report, 2nd time in as many days Sonarr has become unresponsive and have had to kill the process and restart the service…
dev version 2.0.0.3037 on Windows 8.1 64bit
Trace logs from first time here http://hastebin.com/vipivotige.tex
Trace logs from second time here - http://hastebin.com/adiqecuqaq.tex
Full logs here https://www.dropbox.com/s/rsbxvff14ehzom6/logs-SQLITE-Locking.rar?dl=0
Thank you for the report, @markus101 has been working on the sqlite locking.
Yeah I am getting the same issue. On windows 7 64 bit running latest develop.
Sonarr lasts up to 24 hrs before crashing out.
Happened again today, so have attached more trace logs
HOWEVER: this is the first time i didnt have to kill the process, it was no longer running, and the service was already stopped,
the last 10+ times this has happened since i tried that command branch, have always had to kill the processs then start the services, this time only had to start the service.
dev 2.0.0.3039 on Windows 8.1
http://hastebin.com/dibodoleci.coffee
EDIT: Second Crash Today: http://hastebin.com/opetewudun.tex
EDIT 2: another crash 2.0.0.3046 - no locking errors in log really, but its same problem, sonarr webpage only loads first dot, log only shows attempts to access interface, same as the above ones. http://hastebin.com/eqonalofuz.tex
EDIT 3: another one - service was stopped didnt have to kill the process. http://hastebin.com/ivaxaxehur.tex
looks like ‘DB locking due to Progress Messaging’ fix didnt fix it for me
sonarr 2.0.0.3065 crashed again, db lock error, then same as usual, black gui, cant stop service, have to kill process. http://hastebin.com/ayayonijaf.tex
if noone else has this i think im just going to delete the db and start again
I’d be awesome to get a memory dump of the crash. Ezhik had one the last time around and it made a world of difference.
yep can do, wont start clean
not sure how im suppose to go about his for app crash and not a system crash, any instructions?
OS is Win 8.1 Pro 64bit
I set this up hopefully correctly, but it didnt create the dump file, i wonder if this is because its not fully crashed the process itself still runs http://gyazo.com/f019fbff05ab1ef0a1a39e9de4df218c
All i could do is Manually Create the dump for nzbdrone.console.exe from task manager, here is a couple from last few days.
log from the 2nd dump file 2.0.0.3077
Been well over a week since i last had a crash, i did change something 10 days ago i switched logging back to debug instead of trace, not 1 crash since then, but might be concidence you might have fixed it in a update since then…
Awesome, we had some issues with 2.0.0.3082 (re-introduced an old issue). Have one more trace to look at from ezhik, some locks are expected (and actually not errors, more of a try again later), its when they come in waves we have a major problem.