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

Bug #1116468 reported by su_v
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
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.

Revision history for this message
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)
Revision history for this message
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

Revision history for this message
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)
Changed in inkscape:
status: New → Confirmed
su_v (suv-lp)
tags: added: svgfonts ui
su_v (suv-lp)
tags: added: gtk-quartz
removed: gtk-osx
Revision history for this message
Fletcher Porter (fpdotmonkey) wrote :

Same crash. Inkscape 0.92 on macOS 10.13.3

Library versions:
glib 2.54.0
glibmm 2.54.1
gtkmm 2.24.5
gtk 2.24.21_1

Revision history for this message
Qantas94Heavy (qantas94heavy) wrote :

Assuming fixed with native macOS version for Inkscape 1.0. If this is still an issue, please check the listed bugs here: https://inkscape.org/report

Closed by: https://gitlab.com/Qantas94Heavy

Changed in inkscape:
status: Confirmed → Fix Released
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.