You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue here is that there is no way for fish to tell that's a multi-line construct.
The first line fails parsing, but since fish doesn't have heredocs the second line is looked at separately, and that then possibly causes some combinatoric explosion.
The solution is to tighten the checks for history import further.
When I run
fish
, it hangs at 100% CPU, and doesn't respond to SIGINT. If I move~/.bash_history
elsewhere, it starts up fine.This seems similar to e.g. #7407 and #7497, but both of those issues appear fixed in fish 3.2.1.
My bash history is ~2.6MB, just under 95k lines long (though a little under 10k of those are
HISTTIMEFORMAT
comments).I believe the problematic command (or, one of the problematic commands) is this one:
The problem seems to be specific to the JSON – a history file containing a heredoc of 4kb of
aaaaaaaa
causes no issues.The text was updated successfully, but these errors were encountered: