# webRequest.onCompleted event stops working until after restarting

**URL:** https://discourse.mozilla.org/t/webrequest-oncompleted-event-stops-working-until-after-restarting/18996
**Category:** Development
**Created:** [September 8, 2017, 2:54pm UTC](https://discourse.mozilla.org/t/webrequest-oncompleted-event-stops-working-until-after-restarting/18996 "2017-09-08T14:54:33Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jdorw](https://avatars.discourse-cdn.com/v4/letter/j/b19c9b/32.png) [@jdorw](https://discourse.mozilla.org/u/jdorw)
#### Post date: [September 8, 2017, 2:54pm UTC](https://discourse.mozilla.org/t/webrequest-oncompleted-event-stops-working-until-after-restarting/18996/1 "2017-09-08T14:54:34Z")

</div>

I’ve been getting bug reports of our extension acting weird when a user is upgraded to a new version. I’ve been able to isolate it to a problem with the `webRequest.onComplete` event.

The problem is that the event stops firing until the browser has been restarted. After restarting the event works as expected.

Any idea why this happens or do I need to tell users to restart after an upgrade?

Here’s where I’m using that event:

> <https://github.com/duckduckgo/chrome-zeroclickinfo/blob/beta/js/tabManager.js#L125>

---

<div class="post-metadata">

### Author: ![jorgev](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jorgev](https://discourse.mozilla.org/u/jorgev)
#### Post date: [September 12, 2017, 11:25am UTC](https://discourse.mozilla.org/t/webrequest-oncompleted-event-stops-working-until-after-restarting/18996/2 "2017-09-12T11:25:44Z")

</div>

Please [file a bug report](https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=WebExtensions:%20Untriaged) for this. Attaching a test case would help figure this out faster.