Bug 184362 - x11/mate-terminal crash
Summary: x11/mate-terminal crash
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-28 22:50 UTC by Michael Moll
Modified: 2014-10-27 14:01 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Moll freebsd_committer freebsd_triage 2013-11-28 22:50:02 UTC 
if I'm opening some new tabs quickly, the following happens:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 808c13000 (LWP 100901/mate-terminal)]
0x000000080516944a in g_source_unref_internal ()
   from /usr/local/lib/libglib-2.0.so.0
(gdb) bt
#0  0x000000080516944a in g_source_unref_internal ()
   from /usr/local/lib/libglib-2.0.so.0
#1  0x000000080516a4c0 in g_main_context_check ()
   from /usr/local/lib/libglib-2.0.so.0
#2  0x000000080516ab53 in g_main_context_iterate ()
   from /usr/local/lib/libglib-2.0.so.0
#3  0x000000080516abf4 in g_main_context_iteration ()
   from /usr/local/lib/libglib-2.0.so.0
#4  0x000000080980699d in g_io_module_query ()
   from /usr/local/lib/gio/modules/libdconfsettings.so
#5  0x000000080518e78a in g_thread_proxy ()
   from /usr/local/lib/libglib-2.0.so.0
#6  0x00000008079784b4 in pthread_create () from /lib/libthr.so.3
#7  0x0000000000000000 in ?? ()
(gdb)
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-11-28 22:50:10 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->gnome

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Jan 2014-06-09 12:58:41 UTC 
I have the same problem. Opening mate terminal tabs to fast, or after awhile after opening a new tab, mate-terminal crash.

Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x000000080400ea4d in g_list_sort_with_data () from /usr/local/lib/libglib-2.0.so.0
[New Thread 809218c00 (LWP 100742/mate-terminal)]
[New Thread 80a043000 (LWP 100668/mate-terminal)]
[New Thread 809013400 (LWP 100636/mate-terminal)]
[New Thread 809006400 (LWP 101240/mate-terminal)]
(gdb) bt
#0  0x000000080400ea4d in g_list_sort_with_data () from /usr/local/lib/libglib-2.0.so.0
#1  0x0000000804012497 in g_main_context_pending () from /usr/local/lib/libglib-2.0.so.0
#2  0x00000008040127af in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.0
#3  0x00000008036902eb in _g_signal_accumulator_false_handled () from /usr/local/lib/libgio-2.0.so.0
#4  0x000000080403745a in g_thread_proxy () from /usr/local/lib/libglib-2.0.so.0
#5  0x00000008050f54a4 in pthread_create () from /lib/libthr.so.3
#6  0x0000000000000000 in ?? ()
(gdb)
Comment 3 Michael Moll freebsd_committer freebsd_triage 2014-06-21 16:25:32 UTC 
Since r264134 I'm running with vm.pmap.pcid_enabled=1 and have no mate-terminal crashes to report.

In a private conversation regarding that problem, Jan told he's running 10.0-RELEASE (which doesn't have the PCID fixes).

Maybe it's time for a wider CFT also in regard of JDK users?
Comment 4 Jan 2014-09-26 09:16:42 UTC 
sorry for the late reply. Updating to > r264134 fix the problem for me.
vm.pmap.pcid_enabled is set to zero on my system
Comment 5 Michael Moll freebsd_committer freebsd_triage 2014-10-27 14:01:58 UTC 
This got fixed a while ago.