Opened 2 years ago

Closed 2 years ago

#6243 closed defect (invalid)

Native crash on disposed FilterEngine access

Reported by: asmirnov Assignee:
Priority: P4 Milestone:
Module: Libadblockplus-Android Keywords:
Cc: sergz Blocked By:
Blocking: Platform: Android
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



Access to disposed filter engine native crash.

How to reproduce

  1. Create java filter engine instance (and waitForReady if it's created asynchronously)
  2. Remember filter engine instance ptr
  3. Dispose adblock engine (and filter engine)
  4. Call any filter engine object method (eg. getHostURL)


Observed behaviour

Native crash

Expected behaviour

Don't access released filter engine, no native crash happens

Attachments (3)

351515661231_.pic_hd.jpg (21.2 KB) - added by asmirnov 2 years ago.
crash.txt (2.4 KB) - added by asmirnov 2 years ago.
reproduced crash stacktrace
WechatIMG149.png (85.2 KB) - added by vickyyu 2 years ago.

Download all attachments as: .zip

Change History (9)

Changed 2 years ago by asmirnov

comment:1 Changed 2 years ago by asmirnov

  • Cc sergz added
  • Ready set

comment:2 Changed 2 years ago by asmirnov

This can be reproduce with the following code:

FilterEngine filterEngine = AdblockHelper.get().getEngine().getFilterEngine();
String host = filterEngine.getHostFromURL(""); // crash here

Changed 2 years ago by asmirnov

reproduced crash stacktrace

comment:4 Changed 2 years ago by asmirnov

The crash happens if accessing filter engine after it's disposed.

It's up to developer to check that dispose() count is equal to release() jus like in C++ with new and delete. If using AdblockHelper you can use getCounter() to check instances count. Also AdblockHelper.get().getAdblockEngine() returns null after it's disposed.

I don't think we should do anything special to make it more safe (like check if filter engine is disposed every time when accessing).
If this happens in AdblockWebView this should be fixed in separate issue.

comment:5 Changed 2 years ago by asmirnov

BTW AdblockWebView doesn't dispose external Adblock Engine instance:

So in use case where multiple AdblockWebviews are created in Activity it's up to activity to create AdblockEngine instance in the very beginning, set it to each AdblockWebView and dispose it in the very end of Activity lifecycle (so every AdblockWebView does not release it).

Changed 2 years ago by vickyyu

comment:6 Changed 2 years ago by asmirnov

  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.