Handling Device Low Disk Storage
See original GitHub issueThis is actually kind of a feature request. I am observing below exception on an emulator, but it could well be on a real world device and I wonder, if osmdroid could do some checking of free memory or at least cleanup, when below the exception occurs:
10-06 04:27:01.710 7978-9239/de.spieleck.app.badgers.debug E/SQLiteDatabase: Error inserting expires=1475812252000 key=47358738 tile=[B@27aea82 provider=Mapnik android.database.sqlite.SQLiteFullException: database or disk is full (code 13) at android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method) at android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId(SQLiteConnection.java:780) at android.database.sqlite.SQLiteSession.executeForLastInsertedRowId(SQLiteSession.java:788) at android.database.sqlite.SQLiteStatement.executeInsert(SQLiteStatement.java:86) at android.database.sqlite.SQLiteDatabase.insertWithOnConflict(SQLiteDatabase.java:1471) at android.database.sqlite.SQLiteDatabase.insert(SQLiteDatabase.java:1341) at org.osmdroid.tileprovider.modules.SqlTileWriter.saveFile(SqlTileWriter.java:133) at org.osmdroid.tileprovider.modules.MapTileDownloader$TileLoader.loadTile(MapTileDownloader.java:230) at org.osmdroid.tileprovider.modules.MapTileModuleProviderBase$TileLoader.run(MapTileModuleProviderBase.java:296) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) at java.lang.Thread.run(Thread.java:818)
Issue Analytics
- State:
- Created 7 years ago
- Comments:10
@InI4 might want to look at these changes. could always use another set of eyes
Actually this ticket needs more work. App procure storage isn’t working