After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 688094 - gnumeric-1.11.6 (compiled from source) warns about leaks when opening a small *.gnumeric file
gnumeric-1.11.6 (compiled from source) warns about leaks when opening a small...
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
1.11.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2012-11-11 14:29 UTC by Shlomi Fish
Modified: 2012-11-11 16:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The offending file. (3.37 KB, application/x-gnumeric)
2012-11-11 14:29 UTC, Shlomi Fish
Details

Description Shlomi Fish 2012-11-11 14:29:03 UTC
Created attachment 228697 [details]
The offending file.

With the attached file gnumeric gives me many warnings on exit. I'm on Mageia Linux 3/Cauldron using gnumeric-1.11.6-2.mga3 or ~/apps/gnumeric/bin/gnumeric-1.11.6 built from source with "./configure --prefix="$HOME/apps/gnumeric" --disable-component". I get these warnings:


shlomif@telaviv1:~$ ~/apps/gnumeric/bin/gnumeric-1.11.6 *.gnumericLeaking expression at 0x15bf1e8: '?'!$A:$A.
Leaking expression at 0x15bf228: '?'!$B:$B.
Leaking expression at 0x15bf268: '?'!$B:$B.
Leaking expression at 0x15bf288: '?'!$A:$A.

** (/home/shlomif/apps/gnumeric/bin/gnumeric-1.11.6:28731): WARNING **: Leaked 4 nodes from expression pool for small nodes.
Leaking 8 values.

** (/home/shlomif/apps/gnumeric/bin/gnumeric-1.11.6:28731): CRITICAL **: go_font_free: assertion `font->ref_count == 1' failed

** (/home/shlomif/apps/gnumeric/bin/gnumeric-1.11.6:28731): WARNING **: Missing calls to go_font_cache_unregister
Leaking GOFormat at 0x1560a30 [General].
Leaking string [40] with ref_count=1.
Leaking string [26] with ref_count=1.
Leaking string [42] with ref_count=1.
Leaking string [60] with ref_count=1.
Leaking string [46] with ref_count=1.
Leaking string [62] with ref_count=1.
Leaking string [80] with ref_count=1.
Leaking string [66] with ref_count=1.
Leaking string [82] with ref_count=1.
Leaking string [100] with ref_count=1.
Leaking string [86] with ref_count=1.
Leaking string [10] with ref_count=1.
Leaking string [1000] with ref_count=2.
Leaking string [30] with ref_count=2.
Leaking string [34] with ref_count=1.
Leaking string [50] with ref_count=2.
Leaking string [2000] with ref_count=2.
Leaking string [38] with ref_count=1.
Leaking string [54] with ref_count=1.
Leaking string [70] with ref_count=2.
Leaking string [500] with ref_count=2.
Leaking string [58] with ref_count=1.
Leaking string [74] with ref_count=1.
Leaking string [90] with ref_count=1.
Leaking string [1500] with ref_count=2.
Leaking string [78] with ref_count=1.
Leaking string [0] with ref_count=3.
Leaking string [20] with ref_count=1.
shlomif@telaviv1:~$ 


I was told the problem is that there are two charts referencing the same data.
Comment 1 Jean Bréfort 2012-11-11 16:45:50 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.