Bug 4366 - Crash in gtk rendering some fonts
Summary: Crash in gtk rendering some fonts
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Blocks: 4353 4379
  Show dependency tree
Reported: 2012-04-10 08:10 UTC by Alan McGovern
Modified: 2012-04-23 15:09 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Alan McGovern 2012-04-10 08:10:03 UTC
We have just received a report of this issue but have no details as of yet. I am filing this now and will add more information as we get it. Hopefully there is enough here to start figuring out what is wrong though.

This is apparently a crash in Gtk while MonoDevelop is starting up. I believe the user is on a chinese language machine (still have to confirm that). I am also requesting a list of installed fonts in case that's any use.

Thread 1 (process 286):

#0 0x94424cb5 in __wait4 ()

#1 0x94424cad in waitpid$UNIX2003 ()

#2 0x0009fe9b in mono_handle_native_sigsegv (signal=11, ctx=0xbfffc9e0) at

#3 0x00004f6e in mono_sigsegv_signal_handler (_dummy=10, info=0xbfffc9a0,
context=0xbfffc9e0) at mini.c:5917

#4 <signal handler called>

#5 0x19e972d5 in run_iterator_get_cgglyph ()

#6 0x19e97638 in create_core_text_glyph_list ()

#7 0x19e976f9 in basic_engine_shape ()

#8 0x0474e2f1 in _pango_engine_shape_shape ()

#9 0x04766a4b in pango_shape ()

#10 0x0475764e in shape_run ()

#11 0x047578b6 in process_item ()

#12 0x047581c3 in process_line ()

#13 0x04758beb in pango_layout_check_lines ()

#14 0x047569a1 in pango_layout_get_extents_internal ()

#15 0x04756db4 in pango_layout_get_extents ()

#16 0x0423d17c in gtk_label_size_request ()

#17 0x04108024 in g_cclosure_marshal_VOID__BOXED ()

#18 0x040edc40 in g_type_class_meta_marshal ()

#19 0x040ed937 in g_closure_invoke ()

#20 0x04106599 in signal_emit_unlocked_R ()

#21 0x04105b68 in g_signal_emit_valist ()

#22 0x0410603a in g_signal_emit_by_name ()

#23 0x042df50f in do_size_request ()
Comment 2 Miguel de Icaza [MSFT] 2012-04-10 10:59:26 UTC
Maybe related to this patch from Kris?

Comment 3 Mikayla Hutchinson [MSFT] 2012-04-10 14:14:30 UTC

*** This bug has been marked as a duplicate of bug 3825 ***
Comment 4 Alan McGovern 2012-04-10 15:05:04 UTC
I'm not sure this is a duplicate as the stacktrace is completely different and occurs under completely different circumstances where BOMs should not be present.
Comment 5 Alan McGovern 2012-04-10 15:07:34 UTC
The bug can be reproed by using taiwanese. Set LANG=zh_TW in a terminal and launch MonoDevelop. This happens with our very latest Mono release which went to the updater about 15-20 mins ago.
Comment 6 Kristian Rietveld (inactive) 2012-04-10 16:56:02 UTC
I confirm MonoDevelop crashes with zh_TW.  It is very likely that a specific sequence of characters is causing the crash in the shaping engine.  The shaping engine has to be corrected to also handle this sequence of characters correctly.  The fact that a complex application like Gimp works correctly in zh_TW confirms to me that we have to look for a specific sequence of characters.

I have scrolled through MonoDevelop's entire zh_TW.po with GtkTextView without crashes, so I have not found the affecting string yet.  To be continued ...
Comment 7 Alan McGovern 2012-04-10 20:44:54 UTC
I don't get the crash by building the latest version of everything using bockbuild.

Duncan, What's the difference between the version of Mono we released today and the version I just built from bockbuild 15 minutes ago?
Comment 8 Duncan Mak 2012-04-10 21:04:16 UTC
2.10.9 shipped with Pango 1.29.5 and bockbuild is now at 1.30.

You can recreate the build by reverting to HEAD~2.

If 1.30 is good, we can ship a new Mono with the new Pango.
Comment 9 Kristian Rietveld (inactive) 2012-04-11 14:13:48 UTC
Is it already clear whether the latest rebuilds really fix the problems?   (If so, I can avoid spending time on trying to find the broken string).
Comment 10 Alan McGovern 2012-04-12 05:44:35 UTC
Kristian, i think it's likely that an updated pango fixes the issue, so for now don't bother investigating further. If it turns out the bug has not been fixed, I'll let you know. Thanks!
Comment 11 Duncan Mak 2012-04-23 14:24:14 UTC
We shipped Mono 2.10.9_10 with Pango 1.30.0 last week, which should be enough to close this bug.
Comment 12 Alan McGovern 2012-04-23 15:09:10 UTC
Sounds good! Thanks for the release!