mshockwave/PdfiumAndroid

Shutting down after loading about 80 pages without Exception

Opened this issue · 2 comments

Activity which use this library finishing without Exceptions after paging heavy pdf-document (magazine) for many times (about 80 pages).

Here is Log:

11-03 13:15:09.302 909-1240/system_process E/InputDispatcher﹕ channel '2c1798f6 com.shockwave.pdfiumtest/com.shockwave.pdfiumtest.PdfActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
11-03 13:15:10.094 15037-15154/com.google.android.gms.persistent E/MDM﹕ [336905] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-03 13:15:10.097 15037-15037/com.google.android.gms.persistent E/GmsWearableLS﹕ GoogleApiClient connection failed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-03 13:15:10.421 15037-15037/com.google.android.gms.persistent E/ctxmgr﹕ [PowerConnectionState]Could not write powerInfo=Plug state: 2 BatteryLevel: 0.88, status=Status{statusCode=unknown status code: 7503, resolution=null}
11-03 13:15:10.489 15037-15397/com.google.android.gms.persistent E/MDM﹕ [336937] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-03 13:15:10.563 15037-15403/com.google.android.gms.persistent E/MDM﹕ [336938] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-03 13:15:10.647 909-1250/system_process E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=6,93 rxSuccessRate=28,47 targetRoamBSSID=00:00:00:00:00:00 RSSI=-62
11-03 13:15:10.650 909-1250/system_process E/WifiStateMachine﹕ WifiStateMachine starting scan for "airport 5GHz"WPA_PSK with 5240,2412
11-03 13:15:11.013 15037-15459/com.google.android.gms.persistent E/MDM﹕ [336939] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-03 13:15:11.114 15071-15083/com.google.process.gapps E/DataBuffer﹕ Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@15ab4d6d)
11-03 13:15:11.116 15071-15083/com.google.process.gapps E/DataBuffer﹕ Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@3ad55da2)
11-03 13:15:11.117 15071-15083/com.google.process.gapps E/DataBuffer﹕ Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@1cac6a33)
11-03 13:15:11.118 15071-15083/com.google.process.gapps E/DataBuffer﹕ Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@1436f1f0)
11-03 13:15:11.119 15071-15083/com.google.process.gapps E/DataBuffer﹕ Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@28bc5369)
11-03 13:15:11.120 15071-15083/com.google.process.gapps E/DataBuffer﹕ Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@25cfb1ee)

I have exact same issue

This can be fixed by using:

pdfiumCore.closeDocument(pdfDocument);