VirtualBox 11.3 VM Plasma-desktop crashing with 512MB

Oddly, I am finding that plasma-desktop crashes on a freshly installed 11.3 64-bit VM in VirtualBox whenever memory is set to 512MB. I created the VM with 1GB, which is overkill for what I am using it for. At that point all was well. After lowing memory to 512MB, it boots and starts to load the desktop, which fails - error log below. Increasing memory to 756MB allows it to load fine again.

I don’t really need a desktop environment on this VM, but it seems odd this is happening at all. 512MB should be fine to run a basic VM with KDE and per Hardware requirements - openSUSE 256MB is the minimum, and 512MB is recommended.

While it’s not a big deal, I am a bit curious why this really needs 756MB to run a bare bones system and just launch KDE. Really? We’ve come to that?

Perhaps I just long for the halcyon days when Linux would run, including a desktop environment, on a 486 with 256MB . . .

If anyone happens to have a quick fix though, I’d love to know as I find it a bit curious.

Lews Therin

Application: Plasma Workspace (plasma-desktop), signal: Aborted
[Current thread is 1 (Thread 0x7fc10a924760 (LWP 5984))]

Thread 2 (Thread 0x7fc0f557b710 (LWP 5985)):
#0  0x00007fc106835709 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/
#1  0x00007fc106abf222 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/
#2  0x00007fc106ab50d0 in ?? () from /usr/lib64/
#3  0x00007fc106abebf5 in ?? () from /usr/lib64/
#4  0x00007fc106830a4f in start_thread () from /lib64/
#5  0x00007fc10a24d82d in clone () from /lib64/
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fc10a924760 (LWP 5984)):
[KCrash Handler]
#5  0x00007fc10a1af9e5 in raise () from /lib64/
#6  0x00007fc10a1b0ee6 in abort () from /lib64/
#7  0x00007fc1065dfcdd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/
#8  0x00007fc1065ddef6 in ?? () from /usr/lib64/
#9  0x00007fc1065ddf23 in std::terminate() () from /usr/lib64/
#10 0x00007fc1065de076 in __cxa_rethrow () from /usr/lib64/
#11 0x00007fc106ba5563 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/
#12 0x00007fc106ba988b in QCoreApplication::exec() () from /usr/lib64/
#13 0x00007fc10a51a27d in kdemain () from /usr/lib64/
#14 0x00007fc10a19bb7d in __libc_start_main () from /lib64/
#15 0x0000000000400699 in _start ()

Could it be a VBox bug? I see that 4.0.2 is just out.