vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()

Bug #1721280 reported by Andreas Brauchli on 2017-10-04
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
vim (Ubuntu)
Medium
Unassigned

Bug Description

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

Andreas Brauchli (blk) wrote :

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

Changed in vim (Ubuntu):
importance: Undecided → Medium
summary: - vim.gtk3 crashed with SIGSEGV in kill()
+ vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()
tags: removed: need-amd64-retrace
information type: Private → Public
Török Edwin (edwintorok) wrote :

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) wrote :

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

Changed in vim (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers