[PATCH 0/6] xserver: Memory leaks and input hotplug updates
Magnus Vigerlöf
Magnus.Vigerlof at home.se
Wed Mar 28 14:29:48 PDT 2007
Here are some changes/additions I've found needed for hotplugging
(both adding and removing) input devices successfully without leaking
resources.
Currently outstanding issues:
* D-Bus doesn't seem to like to receive DBUS_HANDLER_RESULT_NEED_MEMORY
(BadAlloc). My client never received any response and the second call
caused the X-server to go into a never-ending loop (the client is a
python script based on Enleth's script)
* In my tests I can still se one memory leak (adding an input device,
wait 1 sec, remove input device) on 0x1c00 bytes. Call-path:
InitValuatorClassDeviceStruct->AllocateMotionHistory
At the moment I'm not 100% sure where the deallocation of this memory
should take place. It might work to put it in CloseDevice with the
other valuator freeing. Good enough?
Btw, is the patch added to Bug#:10324 (x&y axis not scaled when reporting
extension motion events) in the pipe to be applied, or are there changes
needed before it can get that far?
Cheers
Magnus V
More information about the xorg
mailing list