Re: [Scidvspc-users] Possible memory leak problem ?

[Steve A <ste...@gm...>]

We had a nasty leak before, but it was fixed in scidvspc 4.17.

If you are already using this version, pease send me your options files so
I can test the same config/window layout.

Cheers, S.A

On Thursday, April 13, 2017, yoan liba <yo...@gm...> wrote:

> Hi,
>
> I don't find how to submit a bug so i post here.
>
> I have a problem to use scid vs Pc in fedora 25 (up to date).
>
> I use LxQT as a DE, so it's not a gnome 3 problem.
>
> The welcome popup indicate that scid vs Pc has found eveything he needs
> except endgame tablebase.
>
> Scid vs Pc use more and more memory until i don't have enough RAM to use
> my computer at all.
>
> I have try to see if it is a memory leak with valgrind but the result
> seems negative.
>
> I have no problem to compile scid vs Pc with a simple ./configure and a
> make
>
> I copy here the outputs of my terminal after two hours using scid when he
> analyse a game with stockfish or komodo.
>
> [yann@localhost scidvspc]$ valgrind ./scid
> ==1532== Memcheck, a memory error detector
> ==1532== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
> ==1532== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
> ==1532== Command: ./scid
> ==1532==
> [yann@localhost scidvspc]$
>
>
> [yann@localhost scidvspc]$ valgrind --tool=callgrind ./scid
> ==1872== Callgrind, a call-graph generating cache profiler
> ==1872== Copyright (C) 2002-2015, and GNU GPL'd, by Josef Weidendorfer et
> al.
> ==1872== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
> ==1872== Command: ./scid
> ==1872==
> ==1872== For interactive control, run 'callgrind_control -h'.
>
>
> The process who eat all my ram is called tkscid so it's not a chess engine.
>
> This behaviour happens if i compile directly scid vs Pc or if i use a rpm
> in the rpm sphere repository.
>
> Could you tell me what is the problem ?
>
> English is not my native language so don't hesitate to ask if you don't
> understand something  :)
>
> Thanks.
>