MobileRead Forums - View Single Post - PRS-T2 Possible solution - 'ContentService has stopped unexpectedly' indexing crash

rupor · 10-31-2013, 07:58 AM

ebmr

I think there are 2 different issues here (both possibly connected to memory shortage on the device):

1. Failed SQL statement - restarting device (or restarting scanning process) helps, no need for drastic measures.

2. Crash in Adobe RMSDK during indexing and scanning (when meta information is extracted from one of the books and thumbnail is created) possibly due to corrupted memory. This one kills indexing service completely. Device needs to be restarted for sure, if condition persists - books database needs to be rebuilt from the scratch, full content reset may be required...

10-31-2013, 07:58 AM	#7
rupor meat popsicle Posts: 225 Karma: 100000 Join Date: Jul 2007 Location: USA Device: Kindles, Pixels, iPads	ebmr I think there are 2 different issues here (both possibly connected to memory shortage on the device): 1. Failed SQL statement - restarting device (or restarting scanning process) helps, no need for drastic measures. 2. Crash in Adobe RMSDK during indexing and scanning (when meta information is extracted from one of the books and thumbnail is created) possibly due to corrupted memory. This one kills indexing service completely. Device needs to be restarted for sure, if condition persists - books database needs to be rebuilt from the scratch, full content reset may be required...