-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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.
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
freeze when opening /tmp directory #5725
Comments
Do you have many files in your |
nope, only 12 |
Could you provide more details? I can't reproduce this locally with my |
Screen.Recording.2023-01-30.at.11.29.47.AM.movscreen recording shows normal behaviour first, followed by unresponsive behaviour second. Not shown in the screen recording but mentioned above, opening a particular file in a buffer directly without entering into the picker view as shown in the video results in expected behaviour. Unresponsive behaviour only occurs when accessing /tmp directory explicitly |
Interesting so the freeze only occurs after the picker opens so it's unliekly to be realted to the FS transversal. Maybe this is a case of a specific file being too large and locking up the editor when trying to preview it. Like I said it's basically impossible for us to debug the exact cause without having access to the files in your |
Could you share that |
wezterm.nightly.json is actually just a one-liner from a failed build Additional info & testing I'm suspecting there is a misbehaving file that is being generated in /tmp by some other application. I cleared /tmp and tried the same thing again and it was still a no-go, except this time the file picker doesn't even open. (Shown in the clip) However, you'll see a couple files that were auto-generated shortly after emptying the directory the first time which i did not initially catch. This is shown when the file picker won't open on the first attempt of I then emptied /tmp again (notice the auto-generated files are absent this time). screen-recording-2023-01-30-at-124406-pm_L7sBUYS2.movPrior to the above (clearing /tmp so the possibly misbehaving file should still be in /tmp) i did some more playing around testing other terminal emulators and found that the built-in macOS Terminal.app would behaviour on most profiles (build-in profiles seem to only differing in athestics). This is the case for wezterm, kitty, contour terminal emulators all refused to open the picker where Terminal.app seemed to be fine doing so for most profiles. you can me demo 2 different profiles in the clip below, but I tested with a half dozen profiles that are built-in to Terminal.app and all but one profile seemed to behave fine. Screen.Recording.2023-01-30.at.12.20.44.PM.mp4I played around with some of the setting in Terminal.app for a few of the different profiles, different fonts, opacity, colours, etc and I couldn't determine any particular thing causing inconsistent behaviour Update |
(sorry for the potato quality, i had to record and compress to super low quality to come in under the max attachment size) i don't really care if this is fixed, you guys got better stuff to do i'm sure, this is a pretty niche issue that hardly impacts workflow but I thought it might worth flagging incase anyone thinks it's worth looking into since it's bit of weird one. Overall this issue seems to be address by clearing /tmp, I'm good to close due to non-producibility |
Thank you for sticking with us and providing detailed feedback. From your description I think that Ihave a rough idea of what may be causing this (pipes or other types of weird files where reading them blocks) and how to fix it. I still need to do more testing later tough |
I can reproduce, just go into your We actually already do the right thing in the global search. Just not in the file picker. |
Ah I think this might be #5210 |
You are right I didnt realize there was already an open issue. Should we close thisone as a dupliate then? |
I Pulled #5658 and verified that this fixes the case shown of helix freezing before helix is rendered (such as second video). Not sure if it would also take care of the case where hx becomes unresponsive after hx opens with a picker (such as in the first video) since i couldn't reproduce such behaviour after clearing /tmp but as mike mentioned this may be #5210. Seems this issue was actually 2 unique issue that i didn't identify, both of which is being tracked (and one already fixed 👍) Thanks for looking into this gents, |
Summary
when open /tmp (or /tmp/) from command line, hx will open a directory file picker as expected but will become unresponsive to any input, preventing you from interacting with the UI, selecting a file, quitting, etc. requiring the shell instance to be terminated.
I was thinking this might because /tmp is a symlink or dir permissions but I checked with other symlinks and root owned directories and they seem to behave as expected
Reproduction Steps
$ hx /tmp
file picker opens
Expected behaviour:
Actual Behaviour:
Helix log
I cleared the log before reproducing (multiple times) to cut back on un related log messages from days/weeks prior. The log is empty after reproducing this event.
Platform
macOS
Terminal Emulator
wezterm 20221119-145034-49b9839f
Helix Version
helix 22.12 (96ff64a)
The text was updated successfully, but these errors were encountered: