Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak with Ubuntu 20.04 LTS #12

Open
htr3n opened this issue Jun 10, 2020 · 3 comments
Open

Memory leak with Ubuntu 20.04 LTS #12

htr3n opened this issue Jun 10, 2020 · 3 comments

Comments

@htr3n
Copy link

htr3n commented Jun 10, 2020

There is no problem with i3lock-fancy-rapid in Ubuntu 18 LTS but in 20.04 LTS, got this error after unlocking the screen.

$ i3lock-fancy-rapid 5 3
...
~/build/i3lock-fancy-rapid master
=================================================================
==42054==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 4864 byte(s) in 19 object(s) allocated from:
    #0 0x7f4fd4be2bc8 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
    #1 0x7f4fd3e572f4  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x212f4)

Indirect leak of 1184 byte(s) in 37 object(s) allocated from:
    #0 0x7f4fd4be2dc6 in calloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x10ddc6)
    #1 0x7f4fd3e5793c  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2193c)

Indirect leak of 341 byte(s) in 34 object(s) allocated from:
    #0 0x7f4fd4b6b3dd in strdup (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x963dd)
    #1 0x7f4fd3e56b64 in FcValueSave (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x20b64)

SUMMARY: AddressSanitizer: 6389 byte(s) leaked in 90 allocation(s).

I built i3lock-fancy-rapid from source pulled from Github master.

Edited: Before i3lock-fancy-rapid worked with i3 normally but it's no longer working after upgrading to Ubuntu 20.04. Executed i3lock-fancy-rapid from command line like above, I got the error.

@htr3n
Copy link
Author

htr3n commented Jun 10, 2020

Similar to this one: Raymo111/i3lock-color#88

@htr3n htr3n closed this as completed Jun 10, 2020
@htr3n htr3n reopened this Jun 10, 2020
@htr3n
Copy link
Author

htr3n commented Jun 10, 2020

Related to this bug: i3/i3lock#167

@Animeshz
Copy link

Animeshz commented Jul 8, 2021

Seems like upstream has fixed it, is it fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants