Opened on 07/30/2015 at 07:34:19 AM
Closed on 01/07/2016 at 02:29:47 PM
#2837 closed defect (fixed)
App crashes after a few minutes of browsing on site where adds are blocked
Reported by: | passbrains | Assignee: | |
---|---|---|---|
Priority: | P3 | Milestone: | Adblock-Browser-for-iOS-1.2.0 |
Module: | Adblock-Browser-for-iOS | Keywords: | salsita, v |
Cc: | jand, pavelz, vojtab, mario | Blocked By: | |
Blocking: | Platform: | Adblock Browser for iOS | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description (last modified by mario)
Adapted from https://www.passbrains.com/dashboard/view-ticket.php?ticket_no=AKI-32
Environment
Apple + iPhone 4 CDMA + iOS 7.1.2
How to reproduce
- install and open app
- navigate to "net.hr"
- open various articles and go back to home page (browse the site)
Observed behaviour
App crashes after 4-5 minutes of browsing site
(In my settings>about version is v0.11.0 stage-322, but latest i can select in dashboard it is 0.10.0, so i have selected n/a)
Expected behaviour
App should not crash
Attachments (5)
Change History (10)
Changed on 07/30/2015 at 07:34:24 AM by passbrains
Changed on 07/30/2015 at 07:34:27 AM by passbrains
Changed on 07/30/2015 at 07:34:29 AM by passbrains
Changed on 07/30/2015 at 07:34:29 AM by passbrains
Changed on 07/30/2015 at 07:34:30 AM by passbrains
comment:1 Changed on 09/08/2015 at 08:37:50 AM by philll
- Sensitive unset
comment:2 Changed on 10/06/2015 at 08:45:03 AM by mario
- Cc mario added
- Component changed from Unknown to Adblock-Browser-for-iOS
- Description modified (diff)
comment:3 Changed on 10/12/2015 at 11:16:50 AM by mario
- Keywords salsita added
comment:4 Changed on 11/24/2015 at 01:03:22 PM by pavelz
- Keywords v added
comment:5 Changed on 01/07/2016 at 02:29:47 PM by mario
- Milestone set to Adblock-Browser-for-iOS-1.2.0
- Priority changed from Unknown to P3
- Ready set
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
We weren't able to reproduce this issue reliably. However it "should" be solved due to refactoring of corresponding components.
Please keep this in mind during the next QA iteration and re-open this issue if necessary.
The refactoring happened for 1.2.0 which is why I'll assign them to that milestone even though it has been closed already.