And yet, as already pointed out, Vivaldi has no issue here - I use Wayland exclusively. This strongly suggests the problem is not with Vivaldi (but perhaps something interacting with Vivaldi); something else.
In as far as I’m able to guess, the link that @tobenderZephyr has mentioned, which leads to this post is a likely candidate; which would also indicate it is not a Vivaldi issue. Vivaldi, being chromium-based, may only be exhibiting a symptom of the problem.
However, that post is from the Testing Update announcements. If you are using the Testing branch, then it becomes a possibility, however, you have not specified which branch you are using.
At least with this new information, the issue might be easier to diagnose. Unfortunately, not by me, as the errors are non-existent.
Cheers.
You’re already here, so there’s little sense in back-peddling now. 
The link you gave might well be related - in fact, it even seems likely, now that @petaramesh has added some more detail.
Cheers.
It harms nobody to spell things out.
Appendum:- I am error-free using Wayland and AMD graphics. Perhaps this only manifests on Nvidia (guessing). 