when corruption occurs, not clsing the db is casuing stack overflow
due to a bug in DefaultDatabaseErrorHandler, if the corruption is so bad that the list of attached databases can't even be retrieved, then database is not closed in DefaultDatabaseErrorHandler, this causes the corrupted file to remain on disk. this causes corruption detection to occur forever until the stack overflows. Change-Id: I9896bee220231cbde0b1620ad0a617420424967c
Loading
Please register or sign in to comment