mirror of
https://github.com/imputnet/helium.git
synced 2026-11-17 18:59:24 +00:00
[Bug]: First navigation aborts in headless mode with a fresh profile #2891
Labels
No labels
approved
approved
approved
bad ux
bot:review
bot:size
bug
bug
bug
can't replicate
can't replicate
can't replicate
confirmed
confirmed
confirmed
external
feat
feat
feat
good first issue
good first issue
good first issue
invalid
invalid
invalid
needs more info
needs more info
needs more info
pending
pending
pending
upstream
upstream
upstream
WAI
WAI
WAI
wontfix
wontfix
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
imputnet/helium#2891
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Operating system
Linux
Version
0.21.2.1 (Chromium 157.0.8103.50).
Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dircommand line argument and it could not be reproduced thereDescription
In headless mode with a fresh profile, the first CDP navigation can abort with
net::ERR_ABORTED. The request does not reach the server.Crash ID
No response
How to Reproduce?
Requires Linux, Node.js 22 or later, Python 3, and OpenSSL. In an empty working directory, save this as
nav.mjs:Run:
The bug only occurs on a profile's first launch. To repeat, stop helium and the server, then rerun the command (it creates a new profile each time).
Actual behavior
In both cases, uBlock reloads the tab once about 3 seconds after launch. The outcome depends on when navigation starts:
net::ERR_ABORTED. The tab stays onabout:blank, and the server receives noGET /.GET /. The later reload causes a secondGET /.Expected behavior
One navigation, one
GET /, no abort, and no reload.Additional context
--disable-extensionsdoes not unload the bundled uBlock component.vAPI.tabs.reloadfromvAPI.Net.unsuspendAllRequests(vapi-background-dns.js:314), when it releases requests held during first-run startup; making that call a no-op made the navigation succeed 5/5.