vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()

[Andreas Brauchli]

Might be related to one of my extensions

camelcasemotion lightline.vim vim-fetch
inori rust.vim validator.vim vim-fugitive

Please also double check that it's not a duplicate of #96263 "vim crashed with sigsegv"

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: vim-gtk3 2:8.0.0197-4ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 4 16:13:33 2017
ExecutablePath: /usr/bin/vim.gtk3
InstallationDate: Installed on 2017-05-30 (127 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcCmdline: vim update_test_projects.sh
Signal: 11
SourcePackage: vim
StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 mch_exit ()
 getout ()
 <signal handler called> () at /lib/x86_64-linux-gnu/libpthread.so.0
 __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135
Title: vim.gtk3 crashed with SIGSEGV in kill()
UpgradeStatus: Upgraded to artful on 2017-09-25 (8 days ago)
UserGroups: dialout plugdev sudo wireshark

[Apport retracing service (apport)]

StacktraceTop:
 __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135
 __new_sem_wait (sem=sem@entry=0x0) at sem_wait.c:39
 PyThread_acquire_lock_timed (lock=0x0, microseconds=microseconds@entry=-1, intr_flag=intr_flag@entry=0) at ../Python/thread_pthread.h:354
 PyThread_acquire_lock (lock=<optimized out>, waitflag=waitflag@entry=1) at ../Python/thread_pthread.h:563
 new_threadstate (init=1, interp=0x0) at ../Python/pystate.c:258

[Török Edwin (edwintorok)]

I got a similar crash with some other python3 plugins.
To reproduce move your .vim and .vimrc out of the way and then:
$ mkdir -p .vim/pack/bug/start
$ cd .vim/pack/bug/start
$ (git clone https://github.com/Shougo/deoplete.nvim.git && cd deoplete.nvim && git checkout e9e45ebcf7757ca7d32003cb54a0e31bf2afadb8)
$ (git clone https://github.com/roxma/nvim-yarp.git && cd nvim-yarp.nvim && git checkout edb260a)
$ (git clone https://github.com/roxma/vim-hug-neovim-rpc.git && cd vim-hug-neovim-rpc && git checkout 0b8e70f)
$ cd
$ echo 'let g:deoplete#enable_at_startup=1' >.vimrc
$ touch x
$ vim x
Press :q
Repeat a few (sometimes it crashes everytime, sometimes repeat 10-20 times to get a crash), eventually it crashes with SEGV on exit

Run under valgrind, see valgrind.log, that reproduces the problem always:
$ valgrind --log-file=valgrind.log vim x
:q

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Paul White (paulw2u)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue while using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

[Launchpad Janitor (janitor)]

[Expired for vim (Ubuntu) because there has been no activity for 60 days.]