[MacPorts] #46693: gedit @3.14.2_0 crashes when opening a file

MacPorts noreply at macports.org
Fri Jan 30 06:35:36 PST 2015


#46693: gedit @3.14.2_0 crashes when opening a file
-------------------------+----------------------
  Reporter:  braumann@…  |      Owner:  devans@…
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  gedit       |
-------------------------+----------------------

Comment (by devans@…):

 I don't have a 10.6 system available to test but I don't see this problem
 when running on 10.9 or 10.10.

 In my case, when opening a file from the command line, I see the following
 warning only and the file opens correctly
 {{{
 gedit Portfile

 ** (gedit:79874): WARNING **: Set document metadata failed: Setting
 attribute metadata::gedit-language not supported
 }}}

 saving the file works correctly and the following additional warnings are
 emitted
 {{{
 ** (gedit:79879): CRITICAL **: gedit_spell_checker_language_to_key:
 assertion 'lang != NULL' failed

 ** (gedit:79879): WARNING **: Set document metadata failed: Setting
 attribute metadata::gedit-encoding not supported
 }}}

 Similar results when opening a file from the menu or editing a file from
 scratch.

 The messages that I would consider significant are these (from your
 report)
 {{{
 (gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkSeparator':
 out of memory

 (gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkBox': out of
 memory

 (gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkHeaderBar':
 out of memory

 (gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkPaned': out
 of memory

 (gedit:82202): Gtk-WARNING **: drawing failure for widget `GeditWindow':
 out of memory

 (gedit:82202): Gdk-WARNING **: gedit: Fatal IO error 35 (Resource
 temporarily unavailable) on X server /tmp/launch-XogDzn/org.x:0.
 }}}

 Is it possible that you really are running out of memory?  Can you try and
 shut down as many other apps that may be running as possible?  What does
 Activity Monitor say about memory consumption?  Is there a diagnostic
 report available in Console when the app crashes?  Can you post it?

-- 
Ticket URL: <https://trac.macports.org/ticket/46693#comment:2>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list