Comments (5)
We're having a similar problem while using offline tiles. The following code is used to create the mapview instance
simpleReceiver = new SimpleRegisterReceiver(context);
mResourceProxy = new DefaultResourceProxyImpl(inflater.getContext().getApplicationContext());
final XYTileSource MBTILESRENDER = new XYTileSource("mbtiles", org.osmdroid.ResourceProxy.string.offline_mode,
MAP_MIN_ZOOM_LEVEL, MAP_MAX_ZOOM_LEVEL, 256, ".PNG", null);
final File f = MaptilesDatasource.getTilesDatabasePath(context); // the mbtiles file to use
final IArchiveFile[] files = { MBTilesFileArchive.getDatabaseFileArchive(f) };
baseMapModuleProvider = new MapTileFileArchiveProvider(simpleReceiver, MBTILESRENDER, files);
baseMapProvider = new MapTileProviderArray(MBTILESRENDER, null, new MapTileModuleProviderBase[] { baseMapModuleProvider });
return new OfflineTilesMapView(context, 256, mResourceProxy, baseMapProvider); // OfflineTilesMapView is a subclass of MapView
This works fine and the map is displayed correctly.
Then the back button is pressed and in the onDestroy of the activity using the mapview, we call the following code to clean up the providers
baseMapProvider.detach();
baseMapModuleProvider.detach();
The next time we go into the activity to see the map the following warning is repeatedly printed to logcat
RejectedExecutionException
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): java.util.concurrent.RejectedExecutionException: Task org.osmdroid.tileprovider.modules.MapTileFileArchiveProvider$TileLoader@4524d6c8 rejected from java.util.concurrent.ThreadPoolExecutor@440b12f0[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 122]
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1339)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.tileprovider.modules.MapTileModuleProviderBase.loadMapTileAsync(MapTileModuleProviderBase.java:147)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.tileprovider.MapTileProviderArray.getMapTile(MapTileProviderArray.java:119)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.views.overlay.TilesOverlay$1.handleTile(TilesOverlay.java:170)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.util.TileLooper.loop(TileLooper.java:34)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.views.overlay.TilesOverlay.drawTiles(TilesOverlay.java:149)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.views.overlay.TilesOverlay.draw(TilesOverlay.java:136)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.views.overlay.OverlayManager.onDraw(OverlayManager.java:120)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at org.osmdroid.views.MapView.dispatchDraw(MapView.java:924)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13357)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13404)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3077)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13300)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13404)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3077)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13300)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13404)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3077)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13300)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13404)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3077)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13300)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13404)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3077)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13300)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13404)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3077)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13300)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.View.getDisplayList(View.java:13404)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.HardwareRenderer$GlRenderer.buildDisplayList(HardwareRenderer.java:1570)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.HardwareRenderer$GlRenderer.draw(HardwareRenderer.java:1449)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewRootImpl.draw(ViewRootImpl.java:2381)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2253)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1883)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5670)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.Choreographer.doCallbacks(Choreographer.java:574)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.Choreographer.doFrame(Choreographer.java:544)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.os.Handler.handleCallback(Handler.java:733)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.os.Handler.dispatchMessage(Handler.java:95)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.os.Looper.loop(Looper.java:136)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at android.app.ActivityThread.main(ActivityThread.java:5017)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at java.lang.reflect.Method.invokeNative(Native Method)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at java.lang.reflect.Method.invoke(Method.java:515)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
09-01 17:26:38.344: W/o*.o*.t*.m*.MapTileMod*(31446): at dalvik.system.NativeStart.main(Native Method)
Also we are seeing memory issues when we have more than one instance of the mapview using the same tilesource.
Is there some additional clean up code that needs to be called in the activitys onDestroy() method?
from osmdroid.
This can happen if you have any references to osmdroid that are static (MapView). That is, anything that has context shouldn't be static. Does that sound like it's a potential root cause?
from osmdroid.
can you post your map creation code?
from osmdroid.
problem not present for fragments
problem not present for activities
both can be witnessed in the sample application on branch bug/#57
from osmdroid.
reopen if this is still a problem (and what version you're using)
from osmdroid.
Related Issues (20)
- The project is dead? HOT 3
- Maps broken HOT 2
- Could you please explain the source of your map data? HOT 2
- Fix tiny typo in tileinfo about OpenStreetMap HOT 2
- Missing release information - not updated release page HOT 1
- RTL Layout not working properly
- Map blurring during zoom and issues with text clarity when scaling is enabled
- Overlay is not replaced after adding it multiple times HOT 1
- Cluster click doesn't work properly
- Map became much larger than restricted size
- Setting tilesource clears cache
- GitHub Pages site is outdated HOT 1
- What is the current version of osmdroid? HOT 3
- can support the sqlite of arcgis offline tiles when zoom=0 but has more than one tiles?
- MapTileProviderArray with two DownloadProviders / combining regional & global online maps not working
- How should I use user-supplied maps? HOT 3
- One-finger zoom in and out HOT 2
- Is JDK17 supported? HOT 2
- TileLooper calculates wrong number of required tiles when map repetition is disabled HOT 3
- 89°.29".10' HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from osmdroid.