Memory leak on Ubuntu 15.04

[lllmio]

It takes several days to acquire this amount of RAM

[bekharsky]

Can confirm on 14.04. Just after 3-4 hours:

After two-three days system may freeze and I need to manually kill Viber from console.

[karas84]

That's very strange. I'll try looking into it during this week.

[karas84]

I've narrowed it down to an Xlib call that, alas, it is necessary. I'll see if I can get around it but there's the chance that nothing could be done from my side...

[psukys]

The issue persists (Ubuntu 14.04). Is there a limitation on Xlib functionality upon finding the version which doesn't leak? Looking at memory maps, it does not directly point into definite library - suppose that's the program?

[mealstrom]

Linux 3.19.0-51-generic #58-Ubuntu SMP Fri Feb 26 21:22:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 15.04

*cat /proc/23755/status *

Name:   viberwrapper-in
State:  S (sleeping)
Tgid:   23755
Ngid:   0
Pid:    23755
PPid:   1876
TracerPid:  0
Uid:    1000    1000    1000    1000
Gid:    1000    1000    1000    1000
FDSize: 64
Groups: 4 24 27 30 46 108 124 127 999 1000 
VmPeak:  1299728 kB
VmSize:  1281624 kB
VmLck:         0 kB
VmPin:         0 kB
VmHWM:    738016 kB
**VmRSS:      738016 kB**
VmData:  1068208 kB
VmStk:       136 kB
VmExe:      3184 kB
VmLib:     25816 kB
VmPTE:      1892 kB
VmSwap:        0 kB
Threads:    5
SigQ:   0/30131
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000001001000
SigCgt: 0000000180000002
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 0000003fffffffff
Seccomp:    0
Cpus_allowed:   ff
Cpus_allowed_list:  0-7
Mems_allowed:   00000000,00000001
Mems_allowed_list:  0
voluntary_ctxt_switches:    30016
nonvoluntary_ctxt_switches: 104

What info you need for testing?