Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#4010 closed defect (fixed)

ABB iOS crashing with memory pressure more often than before.

Reported by: scheer Assignee:
Priority: P2 Milestone: Adblock-Browser-for-iOS-1.3.2
Module: Adblock-Browser-for-iOS Keywords:
Cc: Blocked By:
Blocking: Platform: Adblock Browser for iOS
Ready: yes Confidential: no
Tester: Unknown Verified working: yes
Review URL(s):

Description (last modified by pavelz)

There is no hard and fast amount of content that needs to be loaded, or in a particular way before it crashes. But, it does happen often.

Jetsam is attached.

This was also tested against Opera iOS with no reproduction.

Environment

ABB 1.3.2 (926)
iPhone 6 Plus
iOS 9.3.1

How to reproduce

  1. Visit content heavy sites such as imgur.com or foxnews.com
  2. Browse through multiple images and or articles

Observed behaviour

After loading a series of images or articles, the browser crashes.

Expected behaviour

The browser should not crash.

Attachments (3)

JETSAM.txt (44.1 KB) - added by scheer 3 years ago.
JETSAM 3.txt (31.2 KB) - added by scheer 3 years ago.
JETSAM 2.txt (31.2 KB) - added by scheer 3 years ago.

Download all attachments as: .zip

Change History (9)

Changed 3 years ago by scheer

comment:1 Changed 3 years ago by mario

  • Description modified (diff)

comment:2 Changed 3 years ago by pavelz

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

Test 1.3.2 build 932

comment:3 Changed 3 years ago by mario

  • Milestone set to Adblock-Browser-for-iOS-1.3.2
  • Priority changed from Unknown to P2
  • Ready set

Changed 3 years ago by scheer

Changed 3 years ago by scheer

comment:4 Changed 3 years ago by scheer

  • Resolution fixed deleted
  • Status changed from closed to reopened

The crash still occurs, but not as often.

New JETSAM reports added.

ABB 1.3.2 (932)
iPhone 6 Plus
iOS 9.3.1

comment:5 Changed 3 years ago by mario

  • Resolution set to fixed
  • Status changed from reopened to closed

The crash still occurs, but not as often.

I've created a follow-up issue (#4012). The crashes which scheer still experiences are most likely not directly related to the memory leak which was fixed in the scope of this issue. Therefore closing this very issue.

comment:6 Changed 3 years ago by scheer

  • Verified working set
Note: See TracTickets for help on using tickets.