Bug#809982: closed by Sebastian Ramacher (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)

2016-01-10 Thread gi1242+debianbugs
On Fri, Jan 08, 2016 at 10:44:00AM +0100, Sebastian Ramacher wrote: > The BTS knows about versions and keeps track of them. See the graph on > the top right of > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809982. Oh I see. Thanks. Best, Gautam -- Mathematicians are like Frenchmen: what

Bug#809982: closed by Sebastian Ramacher (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)

2016-01-08 Thread Sebastian Ramacher
On 2016-01-08 01:00:18, gi1242+debianb...@gmail.com wrote: > Please don't close this bug as long as 0.3.1-2 is still the only version > in Jessie! Some unsuspecting Jessie user will get burnt badly! The BTS knows about versions and keeps track of them. See the graph on the top right of https://bug

Bug#809982: closed by Sebastian Ramacher (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)

2016-01-07 Thread gi1242+debianbugs
Please don't close this bug as long as 0.3.1-2 is still the only version in Jessie! Some unsuspecting Jessie user will get burnt badly! GI -- One man's folly is another man's wife.

Bug#809982: zathura: Memory leak when PDF is refreshed

2016-01-06 Thread gi1242+debianbugs
On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote: > I'd recommend to try the new version available in unstable and check > if the problem still exists. It appears that the problem is fixed in 0.3.4-1 in testing. (If not, I'll reopen a separate bug for 0.3.4-1). The version 0.3.

Bug#809982: zathura: Memory leak when PDF is refreshed

2016-01-05 Thread gi1242+debianbugs
On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote: > Otherwise we need a more verbose valgrind log with the GTK+ leaks > filtered out. How do I get you this log? If you tell me what I should run on my system to get you the info you need, I'm happy to do it. I'll check out the ve

Bug#809982: zathura: Memory leak when PDF is refreshed

2016-01-05 Thread Sebastian Ramacher
Control: tags -1 + moreinfo On 2016-01-05 14:23:20, gi1242+debianb...@gmail.com wrote: > Update: I ran valgrind. Here's the summary: > > ==13647== LEAK SUMMARY: > ==13647==definitely lost: 274,913 bytes in 62 blocks > ==13647==indirectly lost: 29,937 bytes in 1,264 blocks >

Bug#809982: zathura: Memory leak when PDF is refreshed

2016-01-05 Thread gi1242+debianbugs
Update: I ran valgrind. Here's the summary: ==13647== LEAK SUMMARY: ==13647==definitely lost: 274,913 bytes in 62 blocks ==13647==indirectly lost: 29,937 bytes in 1,264 blocks ==13647== possibly lost: 71,528 bytes in 876 blocks ==13647==still reachable: 70,136,

Bug#809982: zathura: Memory leak when PDF is refreshed

2016-01-04 Thread gi1242+debianbugs
Package: zathura Version: 0.3.1-2 Severity: normal Dear Maintainers, There is a memory leak in zathura. Steps to reproduce: 1. Open a PDF file (e.g. output generated by LaTeX) 2. Scroll 3. Refresh the PDF (e.g. by recompiling the LaTeX document) (You might have to do a forward / i