search

i3 / i3lock

improved screen locker
https://i3wm.org/i3lock
BSD 3-Clause "New" or "Revised" License
921 stars 404 forks source link

Memory Leak After Unlocking #199

Closed oohwooh closed 4 years ago

oohwooh commented 6 years ago

I'm submitting a…

[x] Bug
[ ] Feature Request
[ ] Other (Please describe in detail)

Current Behavior

After unlocking, I am receiving the following message in terminal: 

=================================================================
==13625==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 33 byte(s) in 1 object(s) allocated from:
    #0 0x7fcd8c389b50 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50)
    #1 0x7fcd82c25578 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x50578)

SUMMARY: AddressSanitizer: 33 byte(s) leaked in 1 allocation(s).

Reproduction Instructions

1.) Run i3lock 2.) enter password 3.) recieve memory leak warning 4.) profit?

Environment

Output of i3lock --version:

i3lock: version 2.11-c-23-g5bbdd02 (2018-07-10, branch "master") © 2010 Michael Stapelberg
stapelberg commented 5 years ago

Sorry for the late reply. We don’t use g_malloc in i3lock, so the leak must be somewhere else. Perhaps we indirectly cause it, or perhaps we’re just not to blame.

Further investigations and/or pull requests welcome :)

stapelberg commented 4 years ago

Closing as the reporter is inactive.