Cache entry doomed while accessing the file randomly causing file not loading
Categories
(Core :: Networking: Cache, defect, P2)
Tracking
()
People
(Reporter: tamilarasan012, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][necko-priority-review])
Attachments
(1 file)
1.04 MB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
Steps to reproduce:
We do test our web application in Firefox by opening many Firefox instance, when we accessing our app randomly some Javascript and CSS file are not loading. Upon analysing the behaviour by enabling MOZ_LOG look like doom operation happen at the same time which causing the issue. In this log we faced error for two files crm-reviewprocess-jobs-model_0ec2c42a3b2b87c7a0825272f6c779ad_.js and crm-reviewprocess-style-wrapper_ce349ec5fa90c4b5788626e9b4ed60d0_.css
Actual results:
Some Javascript and CSS files are not loading randomly.
Expected results:
Cached files should load properly
Updated•10 months ago
|
Reporter | ||
Comment 1•10 months ago
|
||
This is the following configuration we are using.
browser.cache.disk.capacity = 2048576
browser.cache.disk.parent_directory = <CacheDisk_Path>
browser.cache.check_doc_frequency = 3
network.http.rcwn.enabled = false
browser.cache.disk.smart_size.enabled = false
Updated•10 months ago
|
Updated•10 months ago
|
Updated•9 months ago
|
Updated•6 months ago
|
Comment 2•6 months ago
|
||
I couldn't find the issue in the logs. Kershaw will also take a look
Comment 3•5 months ago
|
||
Sorry for the long delay.
This seems to be the reason of load failure:
2024-01-12 08:22:04.852368 UTC - [Parent 11340: Socket Thread]: I/nsHttp Http2Session 7f3fc7a1e800 buffering frame header read failure 804b0014
The log indicates that the HTTP/2 connection was closed due to NS_ERROR_NET_RESET (804b0014), which usually means the server reset the connection.
The log lacks information from the socket layer, so I can't determine the root cause. Could you try to obtain an HTTP log (with MOZ_LOG=timestamp,sync,nsHttp:5,cache2:5,nsSocketTransport:5,nsHostResolver:5
) along with a Wireshark trace? This will help us confirm if the server is indeed closing the connection.
Thank you.
Comment 4•4 months ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:smayya, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Closing due to lack of information. If we can get more logs then we can re-open, thank you.
Updated•3 months ago
|
Description
•