| 1 |
On 07/06/2016 03:17 AM, Franz Fellner wrote: |
| 2 |
> Hey all, |
| 3 |
> |
| 4 |
> I have issues with some prgrams eating too much memory. This seems to be related to glibc not trimming as necessary which results in way too much memory still occupied by the program after free()ing memory. |
| 5 |
> I can't use gcc (specifically g++) with quite some apps now because it starts collecting memory (+swap) until everything falls apart, and I finally came to the conclusion also gcc might suffer from bad trimming behaviour. |
| 6 |
> As glibc is the package that implements free I want to have a closer look at it. The first idea is to get rid of Gentoo patches which are controlled by USE="vanilla". Playing around with glibc might destroy my system. Downgrades are already unsupported. So my question: |
| 7 |
> |
| 8 |
> Can I safely switch from -vanilla to +vanilla in glibc? |
| 9 |
> |
| 10 |
|
| 11 |
It looks to me like USE=vanilla controls only whether or not bundled |
| 12 |
timezone data is used. If that's the case (double-check!), it's probably |
| 13 |
safe to unmerge timezone-data and re-emerge glibc with USE=vanilla. |
| 14 |
|
| 15 |
To be safe, you can bundle up your existing glibc with quickpkg. Then if |
| 16 |
something goes wrong, you can always boot to a liveCD and unpack the old |
| 17 |
version. |
Archives