MobileRead Forums - View Single Post

chaley · 07-12-2013, 11:57 AM

I don't see this behavior.

Are you the person who allowed google to send us the crash reports? If so, then the problem arises because the database no longer has the table of results from the search. It is really hard to see how this can happen.

One possibility is that your device is very memory challenged, causing the underlying android UI object to get recreated when the search finishes. From what I see in the android source code, this could cause the table to get destroyed even though it is in active use.

Does it do the same thing if you long-press on a tag, for example? That uses a different mechanism to create the table.

07-12-2013, 11:57 AM	#2
chaley Grand Sorcerer Posts: 12,447 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	I don't see this behavior. Are you the person who allowed google to send us the crash reports? If so, then the problem arises because the database no longer has the table of results from the search. It is really hard to see how this can happen. One possibility is that your device is very memory challenged, causing the underlying android UI object to get recreated when the search finishes. From what I see in the android source code, this could cause the table to get destroyed even though it is in active use. Does it do the same thing if you long-press on a tag, for example? That uses a different mechanism to create the table.