evas: Fix potential memleak in event info objects
authorJean-Philippe Andre <jp.andre@samsung.com>
Tue, 16 Aug 2016 05:57:02 +0000 (14:57 +0900)
committerJean-Philippe Andre <jp.andre@samsung.com>
Tue, 16 Aug 2016 06:34:33 +0000 (15:34 +0900)
commit9fbb5e0e5dabc3e019f5d3d26da8066f3a176a28
tree6d015005c72f52fd9c870860fbbdd98d58939619
parent40250fda220832e1a5fcabafd1dc70b2a089012e
evas: Fix potential memleak in event info objects

The new event info being an eo object, it needs to be properly
cleaned. I believe this memleak would not show up much in massif
or other checking tools, as it's a stringshare leak. Also, most
of those event objects will in fact be reused and never deleted.

@fix (backported as c58e293d343396859daabdd348)
src/lib/evas/canvas/efl_event_key.c
src/lib/evas/canvas/efl_event_key.eo