Assertion after chaning display resolution
Hi all,
I saw the following assert after chaning display resolution. This might be the cause, but i am not sure. Threaded VNC is enabled. Anyone ever seen this?
qemu-kvm-1.0: malloc.c:3096: sYSMALLOc: Assertion `(old_top ==
(((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
Thanks,
Peter
Quoted 6 lines · Peter Lieven
Hi all,
I saw the following assert after chaning display resolution. This might be the cause, but i am not sure. Threaded VNC is enabled.
Anyone ever seen this?
Quoted 7 lines
qemu-kvm-1.0: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr)
(((char *) &((av)->bins[((1) - 1) * 2])) -__builtin_offsetof(structmalloc_chunk, fd)))) &&old_size== 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (structmalloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size &0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
A shot in the dark - does valgrind show anything wrong?
Quoted 5 lines
Thanks,
Peter
Quoted 7 lines · Alon Levy
Quoted 6 lines · Peter Lieven
Hi all,
I saw the following assert after chaning display resolution. This might be the cause, but i am not sure. Threaded VNC is enabled.
Anyone ever seen this?
Quoted 8 lines
Quoted 7 lines
qemu-kvm-1.0: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr)
(((char *)&((av)->bins[((1) - 1) * 2])) -__builtin_offsetof(structmalloc_chunk, fd))))&&old_size== 0) || ((unsigned long) (old_size)>= (unsigned long)((((__builtin_offsetof (structmalloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1))& ~((2 * (sizeof(size_t))) - 1)))&& ((old_top)->size& 0x1)&& ((unsigned long)old_end& pagemask) == 0)' failed.A shot in the dark - does valgrind show anything wrong?
Problem is i cannot reproduce this, but I can try running the VM in valgrind and check if there is any problem.
Peter
Quoted 4 lines
Quoted 4 lines
Thanks,
Peter