Opened 2 years ago

Last modified 2 years ago

#4642 new defect

ABB Android Crashes with WindowState error

Reported by: scheer Assignee:
Priority: Unknown Milestone:
Module: Adblock-Browser-for-Android Keywords:
Cc: diegocarloslima, mario, fhd Blocked By:
Blocking: Platform: Adblock Browser for Android
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description

We have had some reports that ABB Android crashes, but exact steps to reproduce could not be established.

After taking some time to look at it, I was also able to crash the app. The below error message is shown and the app is crashed when the user has multiple tabs open (think 10+) and continues to surf on one of the open tabs.

I have attached three logs to reflect the same error. In all of these crashes, I had more than 10 tabs open with varying websites. Normally, these sites were content heavy. I was never able to reproduce this crash with only one tab open. This is currently the only crash/error that I get after investigating the crash issue.

In addition to this, it is also worth noting that upon restart of the browser, all previous tabs are lost.

11-14 09:29:29.276 868-1765/? I/WindowState: WIN DEATH: Window{2f789ee8 u0 org.adblockplus.browser/org.adblockplus.browser.App}
11-14 09:29:29.276 868-1766/? I/ActivityManager: Process org.adblockplus.browser (pid 26299)(adj 0) has died(610,273)
11-14 09:29:29.276 11915-11915/? I/CastMediaRouteProvider: in onDiscoveryRequestChanged: request=null
11-14 09:29:29.276 304-22409/? E/OMXNodeInstance: !!! Observer died. Quickly, do something, ... anything...
11-14 09:29:29.276 304-22409/? E/OMX-VDEC-1080P: send_command: Recieved a Command from Client
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: send_command_proxy(): cmd = 0, Current State 3, Expected State 2
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: send_command_proxy(): OMX_CommandStateSet issued
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: Current State 3, Expected State 2
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: Command Recieved in OMX_StateExecuting
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: send_command_proxy(): Executing --> Idle
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: Driver flush i/p Port complete
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: Initiate Input Flush
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: OMX flush i/p Port complete PenBuf(0)
11-14 09:29:29.276 304-26791/? E/OMX-VDEC-1080P: Driver flush o/p Port complete
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Initiate Output Flush
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Buffer queue size 6 pending buf cnt 6
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: ID(c) P1(b225b630) P2(40000000)
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Buffer queue size 5 pending buf cnt 5
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: ID(c) P1(b225b680) P2(40000000)
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Buffer queue size 4 pending buf cnt 4
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: ID(c) P1(b225b6d0) P2(40000000)
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Buffer queue size 3 pending buf cnt 3
11-14 09:29:29.286 304-22409/? E/OMX-VDEC-1080P: send_command: Command Processed
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: ID(c) P1(b225b720) P2(40000000)
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Buffer queue size 2 pending buf cnt 2
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: ID(c) P1(b225b770) P2(40000000)
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Buffer queue size 1 pending buf cnt 1
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: ID(c) P1(b225b4a0) P2(40000000)
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: OMX flush o/p Port complete PenBuf(0)
11-14 09:29:29.286 304-26791/? E/OMX-VDEC-1080P: Rxd OMX_COMPONENT_GENERATE_STOP_DONE
11-14 09:29:29.286 868-1765/? W/WindowManager: Force-removing child win Window{ebe7ff1 u0 SurfaceView} from container Window{2f789ee8 u0 org.adblockplus.browser/org.adblockplus.browser.App}
11-14 09:29:29.286 278-278/? D/SurfaceFlinger: FPS : 1.25
11-14 09:29:29.286 278-278/? W/SurfaceFlinger: Fail to Open /sys/devices/platform/gpusysfs/fps
11-14 09:29:29.296 868-1766/? W/ActivityManager: Force removing ActivityRecord{7e49934 u0 org.adblockplus.browser/.App t21}: app died, no saved state
11-14 09:29:29.316 278-278/? D/SurfaceFlinger: FPS : 1.25
11-14 09:29:29.316 278-278/? W/SurfaceFlinger: Fail to Open /sys/devices/platform/gpusysfs/fps
11-14 09:29:29.346 868-4388/? W/WindowManager: Failed looking up window
                                               java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@c20b17e does not exist
                                                   at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:10471)
                                                   at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:10462)
                                                   at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1592)
                                                   at android.os.BinderProxy.sendDeathNotice(Binder.java:551)
11-14 09:29:29.346 868-4388/? I/WindowState: WIN DEATH: null
11-14 09:29:29.346 868-1024/? D/PointerIcon: setMouseIconStyle1 pointerType: 1001iconType:101 flag:0
11-14 09:29:29.346 868-1766/? D/CustomFrequencyManagerService: acquireDVFSLockLocked : type : DVFS_MIN_LIMIT  frequency : 1350000  uid : 1000  pid : 868  pkgName : ACTIVITY_RESUME_BOOSTER@7
11-14 09:29:29.346 868-1024/? D/PointerIcon: setMouseCustomIcon IconType is same.101
11-14 09:29:29.346 868-1024/? D/PointerIcon: setHoveringSpenIconStyle1 pointerType: 10001iconType:1 flag:0
11-14 09:29:29.346 868-1024/? D/PointerIcon: setHoveringSpenCustomIcon IconType is same.1
11-14 09:29:29.356 868-1766/? W/ActivityManager: mDVFSHelper.acquire()
11-14 09:29:29.356 868-1766/? V/WindowOrientationListener: mSContextAutoRotationListener.getProposedRotation, mbResultFaceDectection: false
11-14 09:29:29.356 868-1766/? V/WindowOrientationListener: mSContextAutoRotationListener.getProposedRotation, Rotation: -1
11-14 09:29:29.356 868-1766/? V/WindowManager: rotationForOrientationLw(orient=1, last=0); user=0  sensorRotation=-1 mLidState=-1 mDockMode=0 mHdmiPlugged=false
11-14 09:29:29.356 868-1766/? V/WindowOrientationListener: mSContextAutoRotationListener.getProposedRotation, mbResultFaceDectection: false
11-14 09:29:29.356 868-1766/? V/WindowOrientationListener: mSContextAutoRotationListener.getProposedRotation, Rotation: -1
11-14 09:29:29.366 868-1769/? D/ActivityManager: startService callerProcessName:com.google.android.gms, calleePkgName: com.google.android.gms
11-14 09:29:29.376 868-1528/? D/ActivityManager: startService callerProcessName:com.google.android.gms, calleePkgName: com.google.android.gms

Environment

ABB Android 1.1.1 (Google Play Version)
Galaxy S7
Android 6.0.1
Galaxy S5
Android 5.0.1

How to reproduce

  1. Load multiple tabs (10+)
  2. Load content heavy sites in each tab, such as http://www.imgur.com
  3. Open latest opened tab and browser articles

Observed behaviour

The app crashes.

Expected behaviour

The app should not crash.

Attachments (3)

Crash 1 ABB.txt (1017.2 KB) - added by scheer 2 years ago.
Crash 2 ABB.txt (1.0 MB) - added by scheer 2 years ago.
Crash 3 ABB.txt (5.7 KB) - added by scheer 2 years ago.

Download all attachments as: .zip

Change History (5)

Changed 2 years ago by scheer

Changed 2 years ago by scheer

Changed 2 years ago by scheer

comment:1 Changed 2 years ago by fhd

Have you tried to reproduce this on a non-Samsung device? Just asking because judging from anecdotal evidence, Samsung devices experience more crashing than others. I have a Nexus 5X, hardly ever crashes there.

I guess before we even start to investigate this we should see whether this still occurs in a build with the upstream merge, Diego can provide one.

comment:2 Changed 2 years ago by scheer

No, I had only tried to reproduce this with Samsung devices, as this is where people had reported the issue.

It would be nice if the issue is resolved with a build from the upstream merge. Keep me updated and I can come back to check on this issue with the newer build.

Note: See TracTickets for help on using tickets.