[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gambas3 ide 3.19.1 - gbx3 [2993]: warning: 2 allocation(s) non freed.
[Thread Prev] | [Thread Next]
- Subject: Re: gambas3 ide 3.19.1 - gbx3 [2993]: warning: 2 allocation(s) non freed.
- From: munix9 <munix9@xxxxxxxxxxxxxx>
- Date: Wed, 20 Mar 2024 01:48:51 +0100
- To: user@xxxxxxxxxxxxxxxxxxxxxx
Am 20.03.24 um 01:35 schrieb munix9:
Am 20.03.24 um 01:16 schrieb Benoît Minisini:Le 20/03/2024 à 01:11, munix9 a écrit :found this: $ LIBPATH="/usr/lib64" GB_GUI=gb.qt5 gambas3 gbx3 [32019]: warning: 2 allocation(s) non freed. This is a general problem in the gambas-ide: Welcome/FSystemInfo.class searches only in /lib and /usr/libIn x86_64 systems, at least openSUSE and possibly Fedora and others, most libs are located in /lib64 and /usr/lib64.Where /lib and /lib64 are respective links to /usr/lib and /usr/lib64 The search for the libs should therefore be: on 32-bit systems search in /lib (if it is not a link) and /usr/libon 64-bit systems search in /lib64 (if it is not a link) and /usr/lib64 (and perhaps also under /lib and /usr/lib)...Thanks, I will fix that. But it does not explain the memory leak...A shot in the dark: maybe it has to do with the number of files/directories? $ ls -l /usr/lib64 | wc 4964 49367 413561
Ah, RDir works recursively? $ find /usr/lib64/ -type f|wc 63499 64235 3968387 https://gitlab.com/gambas/gambas/-/blob/master/app/src/gambas3/.src/Welcome/FSystemInfo.class?ref_type=heads#L202
Re: gambas3 ide 3.19.1 - gbx3 [2993]: warning: 2 allocation(s) non freed. | munix9 <munix9@xxxxxxxxxxxxxx> |
Re: gambas3 ide 3.19.1 - gbx3 [2993]: warning: 2 allocation(s) non freed. | Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> |
Re: gambas3 ide 3.19.1 - gbx3 [2993]: warning: 2 allocation(s) non freed. | munix9 <munix9@xxxxxxxxxxxxxx> |