Inkscape (GTK+/Quartz): crash in SVG Font Editor (stable & trunk)

Bug #1116468 reported by su_v on 2013-02-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
High
Unassigned

Bug Description

Steps to reproduce:

1) launch Inkscape
2) open 'Text > SVG Font Editor…'
3) click on 'New'
4) select newly added SVG font

--> crash:
(inkscape:39121): glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: std::bad_alloc

Reproduced with GTK+/Quartz on:
- Mac OS X 10.5.8 (32bit Intel):
glib 2.28.8, glibmm 2.28.2, gtk+ 2.24.10, gtkmm 2.24.2, cairo 1.11.4, cairomm 1.10.0
- OS X 10.7.4 (64bit):
glib 2.34.3, glibmm 2.34.1, gtk+ 2.24.14, gtkmm 2.24.2, cairo 1.12.10, cairomm 1.10.0

- Does not happen with Inkscape builds using the X11 backend of GTK+.
- Inkscape stable and trunk are equally affected.
- Reproducible when trying to add a new SVG font, and when selecting an existing SVG Font in a file created under X11.

su_v (suv-lp) wrote :
summary: - inkscape-quartz: crash in SVG Font Editor (stable & trunk)
+ Inkscape (GTK+/Quartz): crash in SVG Font Editor (stable & trunk)
Clayton Walker (clayton.walker) wrote :

Confirming. Same issue, same crash.
All one has to do is click around on the SVG Font Editor dialog for a bit.

(inkscape:99727): glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: std::bad_alloc

Clayton Walker (clayton.walker) wrote :

OS is 10.7.5, OS X Lion.
Lib versions:

glib-2.35.4
glibmm-2.33.3
gtkmm-2.24.2
gtk-2-24 from git

su_v (suv-lp) on 2013-02-05
Changed in inkscape:
status: New → Confirmed
su_v (suv-lp) on 2015-01-01
tags: added: svgfonts ui
su_v (suv-lp) on 2017-01-12
tags: added: gtk-quartz
removed: gtk-osx
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers