Bug 434203 - Never Ending Loading on Falkon Pages
Summary: Never Ending Loading on Falkon Pages
Status: RESOLVED UPSTREAM
Alias: None
Product: Falkon
Classification: Applications
Component: general (show other bugs)
Version: 3.1.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
: 434914 436730 438254 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-03-09 18:42 UTC by Max
Modified: 2021-06-26 16:10 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Falkon Terminal Output (7.69 KB, text/plain)
2021-03-09 21:07 UTC, Max
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Max 2021-03-09 18:42:53 UTC
SUMMARY
After updating qt5-webengine to 5.15.3-2, some pages do not finish loading in Falkon. Some sites will initially load normally(eg. Youtube), but after navigating to another part of the site (eg. from homepage to subscriptions), never stop loading (despite having seemingly finished) and cannot be stopped/reloaded. Other sites (eg. Twitter) never stop loading at all. Others still (eg. Google) load and navigate normally. 

STEPS TO REPRODUCE
1. Update qt-webengine to 5.15.3-2 
2. Restart computer
3. Open Falkon browser
4. Navigate to a website (more complex sites tend to trigger the behavior)
5. If the website initially loads, navigate to another page  

OBSERVED RESULT
The tab icon and Stop button indicate that loading is still occurring after all content is displayed. Clicking the Stop button produces no result.

EXPECTED RESULT
Page loads to completion, tab icon ceases loading animation, reload button reverts from Stop to Reload

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (5.11.2-arch1-1)
(available in About System)
KDE Plasma Version: 5.21.2-1
KDE Frameworks Version: 5.79.0-1
Qt Version: 5.15.2-5

ADDITIONAL INFORMATION
--Downgrading to qt5-webengine 5.15.2-5 returns behavior to normal
--Otter browser works as expected on either version. 
--This FreeBSD bug report from 2018 documents a similar problem: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232475
Comment 1 Juraj 2021-03-09 19:30:26 UTC
It looks like there are more problems with QtWE 5.15.3
See https://bugs.archlinux.org/task/69902

Since you did not provide logs I can only assume the cause is the same and look forward for resolution on Qt side.
Comment 2 Max 2021-03-09 20:28:16 UTC
(In reply to Juraj from comment #1)
> It looks like there are more problems with QtWE 5.15.3
> See https://bugs.archlinux.org/task/69902
> 
> Since you did not provide logs I can only assume the cause is the same and
> look forward for resolution on Qt side.

Thanks for responding, Jaraj. You're probably right. Still, I'd be happy to provide any pertinent logs. Just let me know what would be most helpful and whether it's best to add them as attachments. Sorry, baby's first bug report.
Comment 3 Max 2021-03-09 20:33:31 UTC
Juraj*

Sorry for misspelling your name.
Comment 4 Juraj 2021-03-09 20:35:48 UTC
> I'd be happy to provide any pertinent logs.
Try to run falkon from terminal and attach output here as attachment with reasonable name.

> Just let me know what would be most helpful and
> whether it's best to add them as attachments.
Logs are best added as attachments.

> Sorry, baby's first bug report.
Keep practising, it is great skill to have.
Comment 5 Antonio Rojas 2021-03-09 20:36:32 UTC
I highly doubt that this has anything to do with https://bugs.archlinux.org/task/69902. Qtwebengine 5.15.3 is a big update (with a big jump in chromium version) and it's normal that is causes many issues, and not all of them need to be the same one.
Comment 6 Max 2021-03-09 21:07:19 UTC
Created attachment 136544 [details]
Falkon Terminal Output

Here's the requested output.
Comment 7 Antonio Rojas 2021-03-09 22:36:39 UTC
The issue is caused by this change https://code.qt.io/cgit/qt/qtwebengine.git/commit/?id=b719da05c6429d72f4e0e0af44da0bf3f3e57984
Comment 8 Juraj 2021-03-10 08:49:38 UTC
OK, I will try to look into it and newer QtWE when I finish the little things I am working on.

Thank you for investigating this.
Comment 9 Juraj 2021-03-15 21:08:27 UTC
Reported to Qt at https://bugreports.qt.io/browse/QTBUG-91773

This is upstream bug, in essence we do not receive loadfinished or progress (at 100%) signals and thus shows animation all over.

The change mentioned by Antonio Rojas should be the cause.
Comment 10 Max 2021-03-15 23:41:26 UTC
(In reply to Juraj from comment #9)
> Reported to Qt at https://bugreports.qt.io/browse/QTBUG-91773
> 
> This is upstream bug, in essence we do not receive loadfinished or progress
> (at 100%) signals and thus shows animation all over.
> 
> The change mentioned by Antonio Rojas should be the cause.

Awesome. Thank y'all so much. Really cool to experience an issue and be shown the exact cause. I'll be sure to review the upstream report.
Comment 11 Antonio Rojas 2021-03-25 09:32:41 UTC
*** Bug 434914 has been marked as a duplicate of this bug. ***
Comment 12 Antonio Rojas 2021-05-07 13:06:05 UTC
*** Bug 436730 has been marked as a duplicate of this bug. ***
Comment 13 Antonio Rojas 2021-06-26 16:10:25 UTC
*** Bug 438254 has been marked as a duplicate of this bug. ***