microsoft / microsoft/edit

Crash on launch under `screen` ... sometimes

Open
#640 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Rust
Stars
14.6k
Forks
734
Avg merge
8h 40m
Merged PRs (30d)
4

Description

Host: Debian Trixie
Built from `master` using `EDIT_CFG_ICUUC_SONAME=libicuuc.so.76 EDIT_CFG_ICUI18N_SONAME=libicui18n.so.76 EDIT_CFG_ICU_RENAMING_AUTO_DETECT=true cargo build --config .cargo/release.toml --release`

If I run it in a `screen` session, it crashes at launch depending on how I launch the screen session. I haven't quite figured out exactly what is different in the sessions that break it, but this is what it looks like:

Image

Note that the teal `$` is my PS1 prompt here, and the `11;rgb...` is a response from the terminal to some ANSI sequence `edit` sent before it died. The prompt is not "supposed" to be that color -- edit seems to have crashed in the middle of rendering so some color codes for its rendering were left "active".

It's not exiting with any error code -- adding a `; echo $?` to the invocation shows it's exiting with code 0.

Rebuilding without ICU stuff does not affect the results.

Building without the release flags (i.e. just `cargo build`) still doesn't affect the results (I was hoping I'd get some kind of error trace perhaps, but no such luck).

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the launch crash under screen on Debian Trixie using the reported cargo build commands, then compare the screen session launch modes that succeed and fail. The issue provides no source file or test entry point; done means identifying the triggering difference and verifying that edit launches reliably without leaving terminal rendering state behind.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.