Web+: curlThread sometimes pegs CPU

[humdinger]

This is hrev56578+46, 64bit.

Often when browsing the web and you follow some link, the window remains empty, the progress bar is stuck, and a "curlThread" in the WebPositive team is pegging a core. Sometimes simply clicking the link again loads the page alright, sometimes it just times out.

[pulkomandy]

Can you attach the Debugger to the thread while it's in this state, and get a backtrace in a debug report?

[humdinger]

Attached, one debugged curlThread. I get those more often when browsing subredits under ​https://old.reddit.com/ . Also, funnily enough, when trying to attach this report to the ticket...

[pulkomandy]

It is in http2_recv in curl. If that's always the case, maybe we should disable http2 in curl until it is fixed?

[humdinger]

I took 3 such debug reports and they all looked similar.

[humdinger]

Replying to pulkomandy:

It is in http2_recv in curl. If that's always the case, maybe we should disable http2 in curl until it is fixed?

Has anyone tried that yet? This curlThread cpu pegging is the most annoying issue when using Web+ by a very large margin...

[pulkomandy]

I have updated curl, did that fix it? We were using a quite old version of it.

[humdinger]

I recently changed from beta4 to a nightly Haiku and haven't seen this issue since. I planned to wait on your next HaikuWebKit release to go through my Web+ tickets...

Aside from the little kinks (that you have already fixed) and being a bit more sluggish at times, the Web+ experience appears to have improved nicely. Thanks!

[pulkomandy]

Ok then, closing for now, we can reopen if it happens again.

[grexe]

I just experienced high CPU load on the curl thread again, using latest nightly hrev58388.