homebrew-virt-manager icon indicating copy to clipboard operation
homebrew-virt-manager copied to clipboard

pointer being freed was not allocated in macosx sonoma 14.4

Open srilanksa opened this issue 10 months ago • 4 comments

I followed this guide to setting up virt-manager on macosx but at the end i always get this error when trying to display a vm graphically, so it works fine until you click Open then Play in a VM

Terminal: [Sat, Apr 06 2024 11:00:18 virt-manager 3871] DEBUG (vmwindow:185) Showing VM details: <vmmDomain name=linux_mint id=0x1162976c0> [Sat, Apr 06 2024 11:00:18 virt-manager 3871] DEBUG (engine:316) window counter incremented to 2 [Sat, Apr 06 2024 11:00:18 virt-manager 3871] DEBUG (console:721) Starting connect process for proto=vnc trans= connhost=127.0.0.1 connuser= connport= gaddr=127.0.0.1 gport=5900 gtlsport=None gsocket=None Python(3871,0x7ff8493ad100) malloc: *** error for object 0x7f9221998030: pointer being freed was not allocated Python(3871,0x7ff8493ad100) malloc: *** set a breakpoint in malloc_error_break to debug [1] 3871 abort virt-manager --debug -c "qemu:///session" --no-fork

srilanksa avatar Apr 06 '24 14:04 srilanksa

Hey, I am having the same issue. Did you manage to solve it?

ntrifonova avatar Apr 19 '24 05:04 ntrifonova

Hey, I am having the same issue. Did you manage to solve it?

no

srilanksa avatar May 09 '24 20:05 srilanksa

I'm not sure I understand what's going on, but it seems to be related the VNC client being used. The VM seems to start, but virt-manager can't get the display to start. On a whim, I tried a different VNC client (tigerVNC) and I was able to connect to the VM.

If i tired virt-viewer manually, and selected the running VM it would crash out with the same malloc error.

renx99 avatar Jul 10 '24 14:07 renx99

Maybe related to https://github.com/jeffreywildman/homebrew-virt-manager/issues/180

andrioli avatar Aug 23 '24 00:08 andrioli