Closed kumy closed 3 years ago
08-27 20:41:16.930 7426-7797/cgeo.geocaching E/TileDownloader﹕ null
java.io.InterruptedIOException
at com.android.okio.Deadline.throwIfReached(Deadline.java:56)
at com.android.okio.Okio$1.write(Okio.java:67)
at com.android.okio.RealBufferedSink.flush(RealBufferedSink.java:154)
at com.android.okhttp.internal.http.HttpConnection.flush(HttpConnection.java:130)
at com.android.okhttp.internal.http.HttpTransport.flushRequest(HttpTransport.java:73)
at com.android.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:626)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:388)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:332)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:199)
at java.net.URL.openStream(URL.java:470)
at org.mapsforge.android.maps.mapgenerator.tiledownloader.TileDownloader.executeJob(TileDownloader.java:59)
at org.mapsforge.android.maps.mapgenerator.MapWorker.doWork(MapWorker.java:73)
at org.mapsforge.android.maps.PausableThread.run(PausableThread.java:94)
Using OSM, I could lock up the application doing what you described.
Can't find the issue, but I reported that some months ago (or was it only on IRC?).
Still reproducible with the current master.
Assigning myself for field test.
Behaviour still reproducible with 2018.03.16-NB Did not look at the debug log, but assume it is the same.
Still reproducible. Anyway, opening and directly leaving the Livemap multiple times quickly isn't really something which can happen by mistake.
Should we close this as "won't fix" as there are many other issues which are way more important. What do you think?
(I had tried this yesterday as well. Reproducible with current release, but nothing specific in the logcat.)
I agree with @fm-sys
fine for me.
With OSM, I can get c:geo hang when selecting LiveMapActivty, then press immediately back, repeat (fast).
Are you able to reproduce?