Delay in keystroke with web browsers

[roddierod]

Hello,

I upgraded from OpenBSD6.5 to 6.6 and since the upgrade I have been experiencing a delay of keystokes either displaying the character or or functioning (such as going backa space)..but it only happening in web browser textboxes. It happens in both Chromium and Vimb(my main browser). The delay can be of 1-2 seconds per key but it seems cumalative so if I type normally I can wait 10 or 20 seconds for the display to catch up.

I have tried disabling hardware accelaration in chromium settings - that did nothing for this problem. Am using the radeon driver cause I have an older radeon (ATI HD 6950). I tried changing the DRI and Accel options for the driver and that doesn't make a difference.

At this point am looking for any options on what to try. This didn't happen with 6.5 or 6..

Thanks

[victorvas]

Add yourself to an operator group.

[roddierod]

I am in that group.

[shep]

I'm a www/vimb user and also noticed the laggy keyboard in OpenBSD.
Less so in Debian Buster where webkitgtk2 is sandboxed via bubblewrap.

Keyboard lag seems to improve when the cache is cleared.

:clearcache/:cl

I also have a script which clears everything:

#!/bin/sh
> ${HOME}/.config/vimb/closed && > ${HOME}/.config/vimb/command &&  \
 > ${HOME}/.config/vimb/cookies.db && > ${HOME}/.config/vimb/history \
 rm -rf ${HOME}/.local/share/webkitgtk/databases/indexeddb/* && \
 rm -rf ${HOME}/.local/share/webkitgtk/localstorage/*

The script is invoked w/ Ctl-Alt-v in openbox.

I don't see as much lag with Debian and wonder if it is related to pledging development.

www/webkitgtk4 has a security update and I submitted a vimb 3.3 -> 3.5 update
which builds easily in 6.6.

[roddierod]

I also wondered if it was due to pledge, but don't know how to go about checking that out in regards to vimb.

I'll try the cache clearing, thanks.

[jggimi]

While I have no idea what causes the problem, I believe you can rule out pledge(2) as the cause. It doesn't affect performance.

Pledge() is a system call which tells the kernel to "restrict this process to making future system calls only from this whitelist". Any system calls outside the whitelist result in a process abort. That's it.