From: "mame (Yusuke Endoh)" Date: 2021-10-30T16:44:18+00:00 Subject: [ruby-core:105875] [Ruby master Bug#18278] SegFault on exit from gtk3 app Issue #18278 has been updated by mame (Yusuke Endoh). Status changed from Open to Third Party's Issue According to the log, it is very likely to be a problem with gtk3. Could you contact on the author of the gem? I guess the gem wrongly assumes the order in which finalizers are called. ---------------------------------------- Bug #18278: SegFault on exit from gtk3 app https://bugs.ruby-lang.org/issues/18278#change-94414 * Author: sergzhum (Sergey Zhumatiy) * Status: Third Party's Issue * Priority: Normal * ruby -v: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux] * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- I try to implement my gtk3-based app to organize my books/music/etc. After adding the autocompletion feature the app hits segmentation fault occasionly. I've described the way to reproduce it in the BUG-REPRODUCE.md file. Because it is hard for me to extract minimal example and I do not understand the exact cause of segfault, I extracted all needed files (only one ruby file and some data files). Here is the actual git branch with all needed files: https://github.com/zhum/keep-it-well/tree/bugreport `log` - is the dump, the ruby interpreter generated on the last fault. -- https://bugs.ruby-lang.org/ Unsubscribe: