1702051 - DevTools request is missing information

Status: RESOLVED DUPLICATE of bug 1637188

(DevTools :: Netmonitor, defect)

Description

[Roy Wellington]

Attachment: dev-tools-requests.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

0. opened devtools to try to debug a problem
1. made a search in the URL (to Google)

Actual results:

The search sometimes takes an unusually long time to complete, usually if another search hasn't been performed recently. It seems like some sort of caching problem. It might be a problem on my end, and to that, I am trying to use DevTools to get more information about why the request is apparently stalled, and where it is stalled.

Expected results:

DevTools displays basically no information about the request.

There is nothing under any of the "Status", "Type", "Transferred", or "Size" columns. The "Duration" column lists the unusual value of "0 min" (Unusual because times under 1 minute are generally reported using a smaller unit, e.g., "3s", "0ms"). But the request, in actuality, took ~30 seconds, and apparently completed successfully, as subsequent requests for subresources on the page are then issues. (And complete timely, unlike the original request.)

The "Timings" pane displays only "No timings for this request" — but why not?

The "Timings" pane for the request after the problematic request displays "Queued: 30.54 s", so we can see that it is at least a bit aware that something went wrong, though that doesn't offer as good of a clue as we might get had the Timings pane had any information on the original request.

(In the attached PNG, the first request is the weird one I'm trying to debug w/ DevTools.)

Comment 1

[Roy Wellington]

Bugzilla seems to only allow a singular attachment. Here is an Imgur album with more screenshots, more fully showing what I see on the Timings tab for the first & second request.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Search' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 3

[Hubert Boma Manilla (:bomsy)]

Hey Roy,
Thanks for reporting.

Is there more details you can provide (e.g throttling setting, disable cache setting etc). Also does this consistently happen for you? Would you please be able to provide a more detailed / consistent STR if you can?

One scenario which is already known is if you have the disable cache option off, there are requests with missing information See Bug 1637188 for details. Does that match your issue?

Thanks

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(bugs related to missing requests are also grouped in the meta bug 1601925)

Comment 5

[Julian Descottes [:jdescottes]]

No answer so far, should we close as duplicate of Bug 1637188?

Comment 6

[Hubert Boma Manilla (:bomsy)]

(In reply to Julian Descottes [:jdescottes] from comment #5)

No answer so far, should we close as duplicate of Bug 1637188?

Yes. I think we can close as we are not able to reproduce with the STR.

Hello Roy,
Please feel free to reopen if you hit the issue again and its different from
what we see with Bug 1637188