[network markers] We don't know the Cache value on child processes
Categories
(Core :: Gecko Profiler, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | affected |
People
(Reporter: julienw, Unassigned)
References
(Blocks 1 open bug)
Details
It seems that we don't get the cache value for the markers happening on the child processes; we have it properly on the parent process though.
This could be because we use kCacheUnknown in [1], although I don't know if we have access to this data at this location.
Compare with [2] on the parent process.
[1] https://searchfox.org/mozilla-central/rev/1b2636e8517aa48422ed516affe4d28cb7fa220a/netwerk/protocol/http/HttpChannelChild.cpp#1104-1107
[2] https://searchfox.org/mozilla-central/rev/1b2636e8517aa48422ed516affe4d28cb7fa220a/netwerk/protocol/http/nsHttpChannel.cpp#8143-8146
| Reporter | ||
Comment 1•6 years ago
•
|
||
I think we also miss the "count" value for these markers that are emitted for a cached request.
Comment 2•6 years ago
|
||
The bot thinks this bug is a task, but please change it back in case of error.
| Reporter | ||
Updated•6 years ago
|
Comment 4•5 years ago
|
||
This is likely only about propagating this information through OnStartRequest from the parent to the child as another argument in this block
Updated•3 years ago
|
Description
•