> ==3663== 16,384 bytes in 4 blocks are still reachable in loss record 245 of > 246 > ==3663== at 0x482D4B8: calloc (vg_replace_malloc.c:593) > ==3663== by 0x216F23: WriteToClient (io.c:1017) > ==3663== by 0x142667: WriteEventsToClient (events.c:5982) > ==3663== by 0x142747: TryClientEvents (events.c:1968) > ==3663== by 0x144905: DeliverEventToInputClients (events.c:2116) > ==3663== by 0x144A99: DeliverEventsToWindow (events.c:2151) > ==3663== by 0x144D51: ProcSendEvent (events.c:5411) > ==3663== by 0x13B9D5: Dispatch (dispatch.c:432) > ==3663== by 0x130D2F: main (main.c:295)
This appears to be present in 1.14.0, not introduced by this series. I raise a white flag on the other issue though, like the bug Daniel sees I cannot reproduce it here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1015183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
