Opened on 05/24/2016 at 10:33:05 AM

Closed on 07/09/2019 at 07:09:27 PM

#4066 closed defect (rejected)

Too many subscriptions with content blocking enabled causes Safari to crash

Reported by: Ross Assignee:
Priority: Unknown Milestone:
Module: Platform Keywords:
Cc: kzar, sebastian Blocked By:
Blocking: Platform: Safari
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by sebastian)


Safari 9 / OS X 10.11

Reproduced twice.

How to reproduce

  1. Install ABP. Open ABP options.
  2. Enable the Adblock warning subscription.
  3. Add four or five more EasyList subscriptions.
  4. In the [General] tab, enable content blocking.
  5. Observe the error about too many rules appear.
  6. Quit Safari.
  7. Restart Safari.
  8. Observe Safari starts, then quits 1-2 seconds later.

Observed behaviour

Safari starts, displays the OS X spinner and then quits. Sometimes the ABP popup can be opened before the quit.

Expected behaviour

ABP and its functionality/options to not cause Safari to quit.


See 3687#comment:31

Attachments (0)

Change History (6)

comment:1 Changed on 05/24/2016 at 10:33:44 AM by Ross

The second time the testing VM warned about low disk space, attempting to figure out if that is related or the cause (I'm assuming content blocker creates a several MB json file somewhere?)

Last edited on 05/24/2016 at 10:44:42 AM by Ross

comment:2 Changed on 05/25/2016 at 10:16:35 AM by sebastian

  • Cc kzar sebastian added

comment:3 Changed on 05/25/2016 at 12:19:56 PM by kzar

  • Component changed from Unknown to Platform
  • Description modified (diff)
  • Platform changed from Chrome to Safari
  • Summary changed from Too many subscriptions with content blocker enabled causes Safari to quit to Too many subscriptions with content blocking enabled causes Safari to crash

comment:4 Changed on 05/25/2016 at 12:20:54 PM by kzar

  • Description modified (diff)

comment:5 Changed on 05/25/2016 at 12:29:22 PM by sebastian

  • Description modified (diff)

comment:6 Changed on 07/09/2019 at 07:09:27 PM by sebastian

  • Resolution set to rejected
  • Status changed from new to closed

I'm closing all issues related to the legacy Safari extension, as it has been discontinued in favor of an App Extension that doesn't share any code with the old extension.

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none).
Note: See TracTickets for help on using tickets.