inkscape suddenly uses all memory when changing font

Bug #274149 reported by amelieb
4
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
Medium
Unassigned

Bug Description

When I change the font (like testing 4-5 fonts one after the other ), Inkscape freezes and starts to use something like 85% of my 4 Go of RAM (I've checked the memory usage with «top»). After a few seconds/minute, it can work again almost as usual but if I try again to change the font it will start again to use 85% of the memory.

Inkscape 0.46
Ubuntu 8.04.1, 64-bit

amelieb (thymbasilic)
description: updated
amelieb (thymbasilic)
description: updated
Revision history for this message
amelieb (thymbasilic) wrote :

I've had the same problem with Gimp, so it seemed to be a problem with Gnome's font manager or something like that.

I've try to found which font caused the problem and when I kept the font attached to this comment (OldSlavicRegu.ttf) out of ~/.fonts, everything went fine.

The bug can always be reproduced when the font is in ~/.fonts, then with Inkscape or Gimp going through the font list, when I pass over «OldSlavic Regu» or even just before reaching this font, the software freezes and uses something like 85-95% of the memory.

Revision history for this message
nightrow (jb-benoit) wrote :

Hi,
Do you consider this behavior as a problem with the font or a problem with inkscape ?
In the former case we can close the bug repport, otherwise we may have to do something about it.
thanks

Revision history for this message
jpfle (jpfle) wrote :

Hi nightrow,

I don't know if the problem is a kind of corrupt font, but I think that Inkscape should not in this situation freeze as it does and use 90% of the memory.

tags: added: fonts performance
Revision history for this message
su_v (suv-lp) wrote :

previewing the font 'OldSlavicRegu.ttf' in the font selector dropdown list and rendering a text object with this font in Inkscape 0.47 on OS X 10.5.8 does not freeze the ui but gives these these console messages:

inkscape-bin(20581,0xa055a720) malloc: *** mmap(size=4294955008) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
inkscape-bin(20581,0xa055a720) malloc: *** mmap(size=4294955008) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
inkscape-bin(20581,0xa055a720) malloc: *** mmap(size=4294955008) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
inkscape-bin(20581,0xa055a720) malloc: *** mmap(size=4294955008) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Beluga (buovjaga) wrote :

I don't get those warnings in the console. Plz re-test.

Arch Linux 64-bit, KDE Plasma 5
Inkscape 0.92pre1 15054 (GTK3)

Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Windows XP (32-bit), Inkscape 0.91.
Different issue with lp:inkscape/0.92.x, rev. 15207. Inkscape now crashes when selecting the font in the text toolbar's font selector or in the text dialog (when applying the font change).

Short debug trace (well, yes, on Windows...):
----
(gdb) bt
#0 0x6598b24b in FT_Glyph_Get_CBox () from d:\dev\Inkscape\0.92.x\inkscape\freetype6.dll
#1 0x0071e657 in font_instance::FindFontMetrics() ()
#2 0x00000000 in ?? ()
----

So there's something wrong in the font that Inkscape doesn't handle correctly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.