This should fix the discrepancies that we were seeing between runs on the crawler. Turns out that our HTTP request listener was filtering out requests that were initiated using the Beacon API (as opposed to XHR or Fetch). Certain requests would occasionally use Fetch on one run, but Beacon on the other, and so the extension would miss the latter requests completely. This should be completely fixed now.
This should fix the discrepancies that we were seeing between runs on the crawler. Turns out that our HTTP request listener was filtering out requests that were initiated using the Beacon API (as opposed to XHR or Fetch). Certain requests would occasionally use Fetch on one run, but Beacon on the other, and so the extension would miss the latter requests completely. This should be completely fixed now.