Segfault in libglib-2.0 when exiting gedit
Exiting gedit results in a segfault in libglib-2.0.
- Example Error Message:
Jul 19 19:51:32 localhost kernel: gedit[16338]: segfault at 7f1cdceb6880 ip 00007f1ced1d7f0c sp 00007ffc1e6ed3e0 error 4 in libglib-2.0.so.0.5200.3[7f1ced18e000+110000]
-
Steps to reproduce: Launch and exit gedit.
-
uname -a: Linux 4.14.52-gentoo #3 SMP PREEMPT Wed Jul 4 13:33:46 JST 2018 x86_64 Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz GenuineIntel GNU/Linux
-
gedit version: 3.22.1
[ebuild R ] app-editors/gedit-3.22.1::gentoo USE="introspection python spell {-test} -vala" PYTHON_SINGLE_TARGET="python3_6 -python3_4 -python3_5" PYTHON_TARGETS="python3_6 -python3_4 -python3_5" 0 KiB
glib version: 2.52.3
-
$ ldd /usr/bin/gedit | grep libglib libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f836ba53000)
-
valgrind gedit:
==29385== Memcheck, a memory error detector
==29385== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==29385== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==29385== Command: gedit
==29385==
==29385== Invalid read of size 8
==29385== at 0x8249F0C: g_main_context_prepare (in /usr/lib64/libglib-2.0.so.0.5200.3)
==29385== by 0x824A92A: g_main_context_iterate.isra.30 (in /usr/lib64/libglib-2.0.so.0.5200.3)
==29385== by 0x824AB0B: g_main_context_iteration (in /usr/lib64/libglib-2.0.so.0.5200.3)
==29385== by 0x51B8729: g_application_run (in /usr/lib64/libgio-2.0.so.0.5200.3)
==29385== by 0x108D49: main (in /usr/bin/gedit)
==29385== Address 0x17ccb880 is not stack'd, malloc'd or (recently) free'd
==29385==
==29385==
==29385== Process terminating with default action of signal 11 (SIGSEGV)
==29385== Access not within mapped region at address 0x17CCB880
==29385== at 0x8249F0C: g_main_context_prepare (in /usr/lib64/libglib-2.0.so.0.5200.3)
==29385== by 0x824A92A: g_main_context_iterate.isra.30 (in /usr/lib64/libglib-2.0.so.0.5200.3)
==29385== by 0x824AB0B: g_main_context_iteration (in /usr/lib64/libglib-2.0.so.0.5200.3)
==29385== by 0x51B8729: g_application_run (in /usr/lib64/libgio-2.0.so.0.5200.3)
==29385== by 0x108D49: main (in /usr/bin/gedit)
==29385== If you believe this happened as a result of a stack
==29385== overflow in your program's main thread (unlikely but
==29385== possible), you can try to increase the size of the
==29385== main thread stack using the --main-stacksize= flag.
==29385== The main thread stack size used in this run was 8388608.
==29385==
==29385== HEAP SUMMARY:
==29385== in use at exit: 3,912,990 bytes in 45,340 blocks
==29385== total heap usage: 514,005 allocs, 468,665 frees, 39,666,900 bytes allocated
==29385==
==29385== LEAK SUMMARY:
==29385== definitely lost: 28,024 bytes in 97 blocks
==29385== indirectly lost: 53,438 bytes in 2,360 blocks
==29385== possibly lost: 6,623 bytes in 66 blocks
==29385== still reachable: 3,577,913 bytes in 40,842 blocks
==29385== of which reachable via heuristic:
==29385== length64 : 13,016 bytes in 194 blocks
==29385== newarray : 2,432 bytes in 72 blocks
==29385== suppressed: 0 bytes in 0 blocks
==29385== Rerun with --leak-check=full to see details of leaked memory
==29385==
==29385== For counts of detected and suppressed errors, rerun with: -v
==29385== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault
-
Gentoo emerge-info attached gedit_seg_emerge_info.txt
-
Full valgrind leak check attached valgrind_full.txt
-
This issue was reported previously and not resolved by a different user, and the forum link is: https://archives.gentoo.org/gentoo-user/message/3990aa2d7a5fa0f42c84d81470864c9f