Bodie <[email protected]> wrote: > > I am getting regular crashes with core files when running surf > (midori, luakit, ..) web browser. Environments are guest OpenBSD > amd64 -current in VirtualBox on Windows 10 host and OpenBSD amd64 > -current on Dell E6400, 8GB RAM > > Seems highly dependent on amount of "crap" available on visited web > page. In any case here are some outputs which may help. Of course no > core files. I doubt you want to see ~200 - 400MB file :-) >
Was hoping someone more knowledgeable would answer you. I only have a related semi-rant to offer below. TL;DR: Upgrade to latest snapshots, it should be much better, at least that's my experience. But WebKit on OpenBSD is still leaking memory like crazy. And possibly even leading to OS panics. <rant> I'm also trying Luakit on the side from time to time. I used Midori for a few years when it was maintained, and I'm still curious about WebKit. A couple of years ago, when I migrated to OpenBSD on my notebook, I noticed Midori was much less usable compared to how I remembered it from Linux. Epiphany was a disaster. Then I discovered Surf and finally Luakit, which is quite a special project, with Vim-like shortcuts and configuration as code. So I've been making attempts to use Luakit in my free time for some months, as I really like it. In 6.3 with upstream patches it is, in my experience, close to what you describe. In addition, WebKitWebProcess process would hang from time to time and couldn't be killed, not even with the fire of -9. More so, I've started to get OS panics on this old notebook I use as a backup computer. Now I wasn't that bothered by the crashes, not even by the OS ones, as this is old hardware. But I noticed a pattern, the panics were happening always when Luakit was running and the referenced line of a kernel source file was the same. So I have upgraded to a snapshot to check if this was fixed. This was early June, and I found out things were even worse for both type of crashes (OS panics and WebKit crashes). As I always have conky running and visible, I've also started to notice wild allocation and de-allocation of large swats of RAM when opening lots of tabs in Luakit. Unfortunately, I couldn't find the time and guts to collect all info and send a report. Time passed, I have upgraded maybe twice since. Latest snapshot is from July 16. I've only got the OS panic once, but not in a good moment to collect info, and not with the latest snapshot. With 6.3 it was a matter of hours, and with the worst snapshot a matter of tens of minutes before that happened. I still have a photo of the screen after such an OS panic: https://i.imgur.com/yzOXed9.jpg As for your problem, the WebKit crashes, I have not got one with latest snapshot. Can't tell for the snapshot before, I can't remember. In Luakit these crashes are not much of an issue. All tabs have to be reloaded, the same as when you restart the browser after saving the current session. You could say it's also a feature for when too much RAM was leaked. Because, and this is a another BIG problem with WebKit browsers in OpenBSD (possibly on other, less supported, OS'es as well), they leak memory like there's no tomorrow. They are getting better in this regard as well, possibly related to that aggressive allocation and de-allocation I've noticed in the recent snapshots. But still a far cry compared to SeaMonkey, my trusted workhorse on this old notebook. </rant> HTH! :-]
pgpRIg27uFQpP.pgp
Description: Semnătură digitală OpenPGP
