[4.3.0] Sailfish browser becomes sluggish / unresponsive

Bug Reports
#1

REPRODUCIBILITY (% or how often): 100
BUILD ID = OS VERSION (Settings > About product): 4.3.0
HARDWARE (XA2, X10, X10 II, …): X, XA2
UI LANGUAGE:en
REGRESSION: (compared to previous public release: Yes, No, ?): yes

DESCRIPTION:

After some time of usage the browser (which starts really nice, fast and responsive) gets slow, sluggish and unresponsive.

PRECONDITIONS:

use the browser for some time and also write

STEPS TO REPRODUCE:

  1. use browser
  2. write text (wait seconds for it to appear)
  3. try to scroll (touch not recognized, scroll stops for seconds)

EXPECTED RESULT:

browser keeps being responsive as it was on a fresh start

ACTUAL RESULT:

browser becomes.slow

ADDITIONAL INFORMATION:

(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

this can be work-arounded for some time (until it happens again) by restarting the browser

#2

Can you give us examples of websites that you visit? This isn’t reproducible to me, but smells like something wrong around JS/CSS. Nevertheless, I think a newer engine is coming soon™.
(But websites examples is very valuable)

#3

Sure :slight_smile:
https://forum.sailfishos.org

#4

I certainly can’t replicate, but I admit that I rarely respond here using my phone.

#5

I wonder if WebView performance is similar. To test the limits of WebView I built (using Alex Crists scaler):

That thing is a react native app (pared down, but…) and it becomes ever less responsive on input. It definitely is JS in this case. I’m going to compare this to running Scaler in the sfos browser.

It becomes sluggish in WebView relatively quickly. But, I also have the problem in the browser that it still won’t load zeit.de.

#6

Which is definitely another topic :frowning:

and working fine in 3.2.1 :wink:

#7

I wasn’t sure if it’s a different topic in the case of tcp/ip timeouts? The reason I bring that into the discussion is that I noticed that some slow (lots of tcp connections) sites load even more slowly in the 4.3 browser than in the 3.4 browser. It’s not evidence yet.

I do have a test case or two to check timings. I noticed that SailHN (a hacker news client in C++) doesn’t finish loading comments on threads in 4.3. Works in 3.4. Checking against another hackernews client (using python), I note that the comment threads also load on 4.3. Why would python fare better than c? My plan is to add some timing debug code to SailHN to see how the connections fare.

On the javascript side, I just tested the alexcrist scaler site directly in the sfos on 3.4 and 4.3. The 3.4 rendering and response to input is BETTER on 3.4 browser than either my 4.3 sfos browser OR my wrapper app.

Now that seems odd. But has nothing to do with TCP :slight_smile:

#8

With my XA2 I also notice that the browser slow down after a while. For example when I type here in the forum or on Deepl.com. My language is German.

1 Like
#9

I’m wondering if this isn’t related to:

It seems form elements are being repeatedly check with FormAssistant.js when it doesn’t seem they should be. As I understand it, FormAssistant is there to check if the Form Field that is in focus is a password form Username field and should not fire on every character input to ‘any’ form field. But it does.

#10

It happens to me that the browser often freezes for several seconds and continues to work after a while but will freeze again here and then.

2 Likes
#11

yeah, I’ve noticed the same behaviour. I’m pretty sure it’s the javascript interpreter. If I just surf static html pages (I have a couple of sites like that), it’s always fine. Really minimal js sites also ‘never’ have this symptom. Anything with react js is slow… stops for a few seconds, recovers, etc.

2 Likes
#12

With the X, fresh restarted and having open 9 tabs, it is almost impossible to write this post or surf this forum…

#13

I just noted that some issues were resolved in updates the last week. Have you seen any improvement?