Any browser hangs up the VM

[Bidjo]

I have VB v6.1.14 Installed on Windows 10 20H2 and guest Kali Linux system.

Always everything was working without problems. Once I noticed that every time I open browser or open a new page (Firefox or Chrome) it freezes the system. Some times I can successfully load 3-4 pages before it freezes. Looking at host process monitor it shows me that the hard disk is being completely loaded reading and writing to kali.vdi file, which is a virtual hard drive for my guest system.

The host system partition has over 60GB left
The guest system partition has over 10 GB left

All snapshots were deleted
Reboots didn't help
Google fu didn't help

Can anybody please help with the issue.

P.s. when start chrome browser and make it freeze, the console widow of this process shows next info:

[1447533:1447533:1126/191836.865683:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[1447577:1447616:1126/191837.658612:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[1447570:1447570:1126/191837.799562:ERROR:vaapi_wrapper.cc(480)] vaInitialize failed: unknown libva error
[1447570:1447570:1126/191837.852164:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

Can it be the reason of the freezes?

[scottgus1]

As a left-field guess I suspect the browser might be trying to use hardware 3D acceleration (I vaguely recall this being mentioned here sometime ago). If your VM doesn't have hardware 3D acceleration then this might cause trouble.

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[Bidjo]

The problem is solved by checking the 3D acceleration box.

Thanks a lot for help!

[scottgus1]

Great! Glad you're up and running.