Could not allocate CursorWindow crash
See original GitHub issueI have seen similar reports on GooglePlay console and can also kind of reproduce this with 2014.04.03-NB:
- Open live map, google sat
- Start scrolling into one direction really fast
- Keep on scrolling until crash
For me it takes real effort scrolling on the map until this happens. Therefore assigning as ‘Low’ by now.
21:00:06.246 Error CursorWindow 18601 Could not allocate CursorWindow '/data/data/cgeo.geocaching/databases/data' of size 2097152 due to error -24.
21:00:06.366 Error cgeo 18601 DataStore.loadInViewport
21:00:06.366 Error cgeo 18601 android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed.
21:00:06.366 Error cgeo 18601 at android.database.CursorWindow.<init>(CursorWindow.java:104)
21:00:06.366 Error cgeo 18601 at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)
21:00:06.366 Error cgeo 18601 at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:139)
21:00:06.366 Error cgeo 18601 at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:133)
21:00:06.366 Error cgeo 18601 at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:197)
21:00:06.366 Error cgeo 18601 at android.database.AbstractCursor.moveToNext(AbstractCursor.java:245)
21:00:06.366 Error cgeo 18601 at cgeo.geocaching.DataStore.cursorToColl(DataStore.java:2143)
21:00:06.366 Error cgeo 18601 at cgeo.geocaching.DataStore.queryToColl(DataStore.java:2138)
21:00:06.366 Error cgeo 18601 at cgeo.geocaching.DataStore.loadInViewport(DataStore.java:2283)
21:00:06.366 Error cgeo 18601 at cgeo.geocaching.DataStore.loadCachedInViewport(DataStore.java:2239)
21:00:06.366 Error cgeo 18601 at cgeo.geocaching.maps.CGeoMap$LoadRunnable.run(CGeoMap.java:1069)
21:00:06.366 Error cgeo 18601 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
21:00:06.366 Error cgeo 18601 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
21:00:06.366 Error cgeo 18601 at java.lang.Thread.run(Thread.java:856)
Issue Analytics
- State:
- Created 9 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
android - Could not allocate CursorWindow - Stack Overflow
Error -12 means cursor leak. Try to close it: try {....} finally { cursor.close();}.
Read more >Developers - Crash CursorWindow.java - Could not allocate ...
This crash happens since we fully migrate our online config to Split.io SDK, is it possible because our apps are having so much...
Read more >Crash in android.database.CursorWindowAllocationException
3606 crashes in 62.0.3 so far. android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed. # Open Cursors=1 (# cursors ...
Read more >Crash of Silence during database update - Could not allocate ...
Crash of Silence during database update - Could not allocate CursorWindow · Bug description · How to reproduce · Device info · Link...
Read more >Diff - platform/frameworks/base - Google Git
OK) { - fprintf(stderr, "could not connect to rtsp server. ... (status || !window) { LOGE("Could not allocate CursorWindow '%s' of size %d...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is a symptom of a memory full error, which happens right there but could happen at any other place. We should (once again) implement Google Maps API v2 and a newer Mapsforge.
Reopening as we still have occurences with the new release.
2015.03.31, 23 reports up to now.
User message seem all to relate to map activities like zooming or panning around the live map.