Closed
Bug 1373365
Opened 8 years ago
Closed 7 years ago
Page load stall, related to Avast antivirus
Categories
(External Software Affecting Firefox :: Other, defect, P2)
Tracking
(firefox54 unaffected, firefox55+ fix-optional)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox54 | --- | unaffected |
firefox55 | + | fix-optional |
People
(Reporter: azakai, Assigned: adamopenweb)
References
Details
(Keywords: regression, Whiteboard: [sitewait][AV:Avast AV WebShield])
Attachments
(2 files)
Details:
1. This is on https://www.kitely.com/
2. When the bug happens, loading the page on Firefox stalls and takes tens of seconds before the page is rendered and loaded, while on other browsers it's very snappy.
3. This happens on my friend's machine but not mine. It appears to show up in his google analytics reports too, where Firefox load time is 3.6x slower than other browsers, so it's not just a problem on his machine, and he's worried about losing users that are on Firefox.
4. Disabling his antivirus (Avast) gets rid of the bug. He doesn't have any Firefox plugin or addon from the antivirus, or any other suspicious addon or plugin.
5. Nothing odd shows up in the network tab in devtools. Using the profiler, the stall time is reported as spent in XRE_InitChildProcess.
This looks like a regression on firefox, since older firefox is still ok today (so it's not a regression in the antivirus or something else). I got my friend to run mozregression, and it bisected to
https://hg.mozilla.org/integration/mozilla-inbound/rev/48ad3b64dea6
which is bug 1349699. To be sure, he bisected twice to confirm and got the exact same result.
Comment 1•8 years ago
|
||
[Tracking Requested - why for this release]: FF55 regression with one of the most popular antivirus.
status-firefox54:
--- → unaffected
status-firefox55:
--- → affected
tracking-firefox55:
--- → ?
Flags: needinfo?(wmccloskey)
Keywords: regression
Priority: -- → P1
There's not much I can do here. This is a problem with Avast.
Flags: needinfo?(wmccloskey)
![]() |
||
Comment 3•8 years ago
|
||
Alon, can you provide the details on what version of avast your friend is running?
Flags: needinfo?(azakai)
![]() |
||
Comment 4•8 years ago
|
||
Also, your friend's about:support text would be helpful.
Reporter | ||
Comment 5•8 years ago
|
||
Attached is his about:support.
Avast version is Avast 17.4.2294 (should be the latest).
Flags: needinfo?(azakai)
![]() |
||
Comment 6•8 years ago
|
||
How does this Kitely service interact with the browser? I keep getting a message: "Start your virtual world viewer, and login using the following information". According to this support page I need a 3rd party app -
https://kitely.atlassian.net/wiki/display/doc/How+to+Enter+Kitely+Virtual+Worlds
Can you provide steps to reproduce?
Reporter | ||
Comment 7•8 years ago
|
||
The steps are just to load the page at that url, https://www.kitely.com/ . When the bug happens, a very long delay occurs before the page is loaded (during which you'll see either nothing in the page or just a spinner).
(To actually use the virtual world service you do need a virtual world viewer app, but all that's unrelated to the bug here.)
![]() |
||
Comment 9•8 years ago
|
||
Alon, do you run the same rev of Avast? I tried testing in a vm with their latest installed, no issues.
Reporter | ||
Comment 10•8 years ago
|
||
I actually don't have a Windows machine or VM to test on, so I couldn't test Avast myself. I only saw the bug on my friend's machine, which was using that version.
Comment 11•8 years ago
|
||
Andrei, can you find someone who can reproduce so we can move this forward? THanks.
Flags: needinfo?(andrei.vaida)
Comment 12•8 years ago
|
||
Hi everyone!
I managed to reproduce the issue described in comment 0 with Firefox 55.0b7 (BuildId:20170706085221) using Avast Program Version: 17.5.2302 (build 17.5.3559.0) and having the Web Shield component on.
Steps to reproduce:
1.Activate Avast's Web Shield component.
2.Launch Firefox
3.Go to https://www.kitely.com/ webpage
I saw that this issue occurs only when having Web Shield component activated and this may not be reproducible at all times.
Please observe the attached video for further details (Note that I am pressing the F5 key to constantly refresh the webpage).
Alon is this somehow the same as what you have encountered?
Flags: needinfo?(andrei.vaida) → needinfo?(azakai)
Comment 13•8 years ago
|
||
Reporter | ||
Comment 14•8 years ago
|
||
Yes, that looks just like the issue I saw on my friend's machine.
Flags: needinfo?(azakai)
Comment 15•8 years ago
|
||
Jim, can you reproduce w/ the steps from Comment #12.
Flags: needinfo?(jmathies)
(In reply to Jim Mathies [:jimm] from comment #16)
> Dee's, do we have any contacts at avast?
Unfortunately all of my Avast contacts have since moved on. Adam could likely assist with the outreach to a relevant contact — and forging a more solid relationship for this issue as well as the future.
Flags: needinfo?(dchinniah) → needinfo?(astevenson)
Updated•8 years ago
|
Assignee | ||
Comment 18•8 years ago
|
||
Reaching out via LinkedIn.
Assignee: nobody → astevenson
Flags: needinfo?(jmathies)
Flags: needinfo?(astevenson)
Whiteboard: [sitewait]
Comment 19•8 years ago
|
||
Hi, Lukas from Avast here. We've been able to reproduce the problem with https://www.kitely.com/ and tracked it down to a potential problem with the handling of padding inside HTTP/2 data frames. When the last data frame on a connection had a non-zero padding we delayed the padded bytes. We are testing the fix now and should release a fixed version of the HTTP/2 parser (part of Avast AV WebShield) in the next release 17.6.
Reporter | ||
Comment 20•8 years ago
|
||
Great progress! :)
Out of curiosity, do we know why this only affected Firefox, and not Chrome or other browsers?
![]() |
||
Comment 21•7 years ago
|
||
(In reply to Lukas Rypacek from comment #19)
> Hi, Lukas from Avast here. We've been able to reproduce the problem with
> https://www.kitely.com/ and tracked it down to a potential problem with the
> handling of padding inside HTTP/2 data frames. When the last data frame on a
> connection had a non-zero padding we delayed the padded bytes. We are
> testing the fix now and should release a fixed version of the HTTP/2 parser
> (part of Avast AV WebShield) in the next release 17.6.
Hey Lukas, can you confirm this fix shipped?
Flags: needinfo?(rypacek)
Priority: P1 → P2
Whiteboard: [sitewait] → [sitewait][AV:Avast AV WebShield]
Comment 22•7 years ago
|
||
Hello Jim,
I can confirm the fix has been released.
Lukas.
Flags: needinfo?(rypacek)
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•