Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Assertion to_scroll >= 0 failed #27638

Closed
theoparis opened this issue Feb 26, 2024 · 3 comments
Closed

Assertion to_scroll >= 0 failed #27638

theoparis opened this issue Feb 26, 2024 · 3 comments
Labels
bug-crash issue reporting a crash or segfault closed:duplicate issues that are closed as duplicates of other issues needs:repro We need minimal steps to reproduce the issue

Comments

@theoparis
Copy link

Problem

See https://asciinema.org/a/643221

I got this with the latest nightly commit and it seems to only happen with small tmux panes.

Steps to reproduce

Build the latest nightly with make -j12 and run it in a small tmux pane. It might be plugin-specific but I have no idea how to find out what plugin is causing this since nvim just dies before I can do anything.

Expected behavior

Neovim opens fine

Neovim version (nvim -v)

NVIM v0.10.0-dev-a554bb3-dirty

Vim (not Nvim) behaves the same?

no

Operating system/version

Linux theo-xps159500 6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 (2024-02-04) x86_64 GNU/Linux

Terminal name/version

foot

$TERM environment variable

tmux-256color

Installation

build from repo
@theoparis theoparis added the bug issues reporting wrong behavior label Feb 26, 2024
@zeertzjq zeertzjq added needs:repro We need minimal steps to reproduce the issue bug-crash issue reporting a crash or segfault and removed bug issues reporting wrong behavior labels Feb 27, 2024
@zeertzjq
Copy link
Member

Can you git bisect to find what commit caused this?

@theoparis
Copy link
Author

theoparis commented Mar 12, 2024 •
edited

I'm not sure how to use git bisect entirely yet, but it seems like I need a good commit to verify against. The problem is I don't have a good commit. The release-0.9 branch has the same issue.

@justinmk
Copy link
Member

This doesn't have any more info than the existing #21056

@justinmk justinmk added the closed:duplicate issues that are closed as duplicates of other issues label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug-crash issue reporting a crash or segfault closed:duplicate issues that are closed as duplicates of other issues needs:repro We need minimal steps to reproduce the issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@justinmk @theoparis @zeertzjq