Re: Build 165 has performance problems
Reply #3 –
@Freeman, it's the same QtWebKit as it was in previous builds (all release after beta 12), so that sounds more like change on their site, perhaps they are abusing JavaScript now.
Also note that QtWebKit backend is still limited to single process, but that might change later this year (hopefully we will have option to choose between WebKit and WebKit2).