DoomEmacs + Rime = Segmentation Fault (Just when I close emacs)
- Dominant language
- Emacs Lisp
- Stars
- 22.7k
- Forks
- 3.1k
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 4
Description
### I confirm that...
- [x] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.
- [x] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.
- [x] The issue can be reproduced on the **latest** available commit of Doom.
- [x] The issue can be reproduced on a stable release of Emacs, such as 27, 28, or 29. *(Unstable versions end in .50, .60, or .9x)*
### Expected behavior
When I close Emacs, it shouldn't result in a segmentation fault.
### Current behavior
Im using ArchLinux with Emacs 29 (last stable release)
I have this flag activated in init.el
```lisp
(chinese +rime +childframe)
```
Doom Emacs works correctly BUT once I closed it just crash at that moment and this log appears in the terminal:
```shell
Fatal error 11: Segmentation fault
Backtrace:
emacs(emacs_backtrace+0x5b) [0x620f05a4473b]
emacs(terminate_due_to_signal+0xae) [0x620f058b9367]
emacs(+0x60237) [0x620f058ba237]
emacs(+0x34fa75) [0x620f05ba9a75]
/usr/lib/libc.so.6(+0x3d1d0) [0x7915a72dc1d0]
/usr/lib/librime.so.1(_ZN4rime4PoetD1Ev+0x37) [0x7915832aff17]
/usr/lib/librime.so.1(+0x13f163) [0x7915832cb163]
/usr/lib/librime.so.1(_ZN4rime14ConcreteEngineD1Ev+0x5a3) [0x79158321dfb3]
/usr/lib/librime.so.1(_ZN4rime14ConcreteEngineD0Ev+0x16) [0x79158321dfe6]
/usr/lib/librime.so.1(+0x7944a) [0x79158320544a]
/usr/lib/librime.so.1(_ZN4rime7Service18CleanupAllSessionsEv+0x3c) [0x79158322f75c]
/usr/lib/librime.so.1(_ZN4rime7ServiceD1Ev+0x14) [0x7915832338b4]
/usr/lib/librime.so.1(+0xa793e) [0x79158323393e]
/usr/lib/libc.so.6(+0x3f891) [0x7915a72de891]
/usr/lib/libc.so.6(+0x3f95e) [0x7915a72de95e]
emacs(terminate_due_to_signal+0x0) [0x620f058b92b9]
emacs(Ffuncall+0x10d) [0x620f05ad547d]
/usr/bin/../lib/emacs/29.4/native-lisp/29.4-576e0a91/preloaded/files-1e8937b2-592f65e7.eln(F736176652d627566666572732d6b696c6c2d656d616373_save_buffers_kill_emacs_0+0x589) [0x7915a2824ee9]
emacs(Ffuncall+0x10d) [0x620f05ad547d]
/usr/bin/../lib/emacs/29.4/native-lisp/29.4-576e0a91/preloaded/files-1e8937b2-592f65e7.eln(F736176652d627566666572732d6b696c6c2d7465726d696e616c_save_buffers_kill_terminal_0+0xa7) [0x7915a28255d7]
emacs(Ffuncall+0x10d) [0x620f05ad547d]
emacs(Ffuncall_interactively+0x40) [0x620f05ac3980]
emacs(Ffuncall+0x10d) [0x620f05ad547d]
emacs(Fcall_interactively+0x1a9d) [0x620f05acd96d]
/usr/bin/../lib/emacs/29.4/native-lisp/29.4-576e0a91/preloaded/simple-fab5b0cf-7c10fc4e.eln(F636f6d6d616e642d65786563757465_command_execute_0+0x2ad) [0x7915a2c1a70d]
emacs(Ffuncall+0x10d) [0x620f05ad547d]
emacs(+0x1c6b54) [0x620f05a20b54]
emacs(internal_condition_case+0x76) [0x620f05ac2ad6]
emacs(command_loop_2+0x3f) [0x620f05a1fd8f]
emacs(internal_catch+0x49) [0x620f05ac2a19]
emacs(+0x1c6248) [0x620f05a20248]
emacs(recursive_edit_1+0xcc) [0x620f05a2035c]
emacs(Frecursive_edit+0x112) [0x620f05a20552]
emacs(main+0x24b7) [0x620f058cb347]
/usr/lib/libc.so.6(+0x25e08) [0x7915a72c4e08]
/usr/lib/libc.so.6(__libc_start_main+0x8c) [0x7915a72c4ecc]
emacs(_start+0x25) [0x620f058cb9f5]
Violación de segmento (`core' generado)
```
I don't know why, but only happens when I have that flag activated and just after close emacs.
### Steps to reproduce
1. Enable this flag in your init.el
```lisp
(chinese +rime +childframe)
```
2. Refresh doom emacs with C-h r r
3. Restart emacs just in case
4. Open emacs from a terminal (in order to see the logs)
5. Close emacs.
At the step 5 should appears a Segmentation Fault in the terminal.
### System Information
https://pastebin.com/DrAwzXQj
Contributor guide
Assessment
This issue has not been assessed yet.