Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #706492 > unrolled thread

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

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#809982: zathura: Memory leak when PDF is refreshed gi1242+debianbugs@gmail.com - 2016-01-05 20:40 +0100
    Bug#809982: zathura: Memory leak when PDF is refreshed Sebastian Ramacher <sramacher@debian.org> - 2016-01-05 22:10 +0100
      Bug#809982: zathura: Memory leak when PDF is refreshed gi1242+debianbugs@gmail.com - 2016-01-05 23:20 +0100
      Bug#809982: zathura: Memory leak when PDF is refreshed gi1242+debianbugs@gmail.com - 2016-01-06 21:00 +0100

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

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,419 bytes in 31,730 blocks
    ==13647==         suppressed: 0 bytes in 0 blocks
    ==13647== Reachable blocks (those to which a pointer was found) are not shown.
    ==13647== To see them, rerun with: --leak-check=full --show-leak-kinds=all

Looks like there definitely is a memory leak which leaks sizable chunks
of memory (not just a KB or two).

GI

-- 
The system requirements said 'Requires Windows 95 or better', so I
bought a Mac.

[toc] | [next] | [standalone]

#706502

[Multipart message — attachments visible in raw view] — view raw

Control: tags -1 + moreinfo

On 2016-01-05 14:23:20, gi1242+debianbugs@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
>     ==13647==      possibly lost: 71,528 bytes in 876 blocks
>     ==13647==    still reachable: 70,136,419 bytes in 31,730 blocks
>     ==13647==         suppressed: 0 bytes in 0 blocks
>     ==13647== Reachable blocks (those to which a pointer was found) are not shown.
>     ==13647== To see them, rerun with: --leak-check=full --show-leak-kinds=all
> 
> Looks like there definitely is a memory leak which leaks sizable chunks
> of memory (not just a KB or two).

Unfortunately that information is not useful. Without knowing where it exactly
leaks, we can not do very much.

I'd recommend to try the new version available in unstable and check if the
problem still exists. Otherwise we need a more verbose valgrind log with the
GTK+ leaks filtered out.

Cheers
-- 
Sebastian Ramacher

[toc] | [prev] | [next] | [standalone]

#706524

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 version in testing later today.

Thanks,

GI

-- 
'Altruism' -- That occasional moment when your selfishness benefits
someone else.

[toc] | [prev] | [next] | [standalone]

#706722

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.1-2 in Jessie still has the memory leak though.

Best,

Gautam

-- 
'Kleptomaniac' -- One who can't help himself from helping himself.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web