Google+ crashs / IllegalStateException Couldn't read row 10914, col 0 from CursorWindow

[helogrin]

Hi!

Since last Samsung Android Update to version

Modellnummer: GTI9300
Android-Version: 4.3
Basisbandversion: I9300XXUGNA8
Kernel version:
3.0.31-2429075
dpi@HP20 #1
Thu Jan 16 23:47:54 KST 2014
Buildnumber
JSS15J.I9300XXXUGNA5

I get every 15-30 minutes this Google+ crash:

Stack trace:
java.lang.IllegalStateException Couldn't read row 10914, col 0 from CursorWindow. Make sure the Cursor is initialized correctly before accessing date from it.
at android.database.CursorWindow.nativeGetString(Native Method)
at android.database.CursorWindow.getString(CursorWindow.java:438)
at android.database.AbstractWindowedCursor.getString(AbstractWindowedCursor:51)
at crt.a(PG:789)
at crz.a(PG:474)
at crt.a(PG:315)
at ely.e(PG:532)
at eed.run(PG:166)
at java.lang.Thread.run(Thread:java:841)

Package name: com.google.android.apps.plus
Package version: 41307633
Package version name: 4.3.1.63038142

Has anybody any idea how I can get rid of this issue? Is there any known issue, workaround or hack?

If I search, I find nothing at all.

Thanks

 

[GSDer]

Welcome to the forums!

That's an odd one - I've never seen a stack trace displayed before.

You could try:
- Clear cache and Clear data for the Google+ app
- uninstall updates then update again for the Google+ app
- check to make sure all other Google services are running (i.e. make sure none of them are disabled/turned off)
- boot into Recovery mode and clear the system cache

If none of that pans out there's always a Factory Reset...

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk

 

[helogrin]

Thanks!

These steps solved my issue:
- Clear cache and Clear data for the Google+ app
- uninstall updates then update again for the Google+ app

Now everything is running again...

But it was also interesting, that I was not able to find any similar report regarding Google+

 

[helogrin]

So. A month later it's back again. :-(

Somehow it looks like, I'm the only one, who has this issue :-|

 

[JS Huang]

You're not the only one.

I do suffer the issue recently.


My model is a S3 varient from Japan: SC-06D SC06DOMBMF1 4.1.2.

It's really sad no real solution yet.