Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pointer being freed was not allocated in macosx sonoma 14.4 #205

Open
srilanksa opened this issue Apr 6, 2024 · 5 comments
Open

pointer being freed was not allocated in macosx sonoma 14.4 #205

srilanksa opened this issue Apr 6, 2024 · 5 comments

Comments

@srilanksa
Copy link

srilanksa commented Apr 6, 2024

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:
[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

@ntrifonova
Copy link

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

@srilanksa
Copy link
Author

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

no

@renx99
Copy link

renx99 commented Jul 10, 2024

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.

@andrioli
Copy link

Maybe related to #180

@piphoser
Copy link

piphoser commented Sep 17, 2024

Same issue here. I tried the various suggestions re: Spice but nothing worked. Note that opening a remote stopped VM works fine, allows editing the configuration, etc. If remote VM is running, I get the
malloc: *** error for object 0x7fd28e8dda30: pointer being freed was not allocated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants