By at least 28 Sept Fluent crashes daily

[jamesisin]

Beginning (possibly with an update to Windows) on or at least by 28 Sept Fluent Terminal crashes once per day (some times more).

The cursors of each terminal continue to flash and I can switch between tabs or create new tabs, but all terminal input is frozen and no operations complete (or no output is registered in any terminal).

The application cannot be exited and must be killed using Windows Task Manager.

I can provide a partial list of dates and approximate times of crashes (very nearly the same time each day though there is some drift).

(After some but not all crashes the icon is unpinned from the Taskbar.)

[jamesisin]

It looks like the application loses its ability to communicate or interact with the shell.

I am able to open a new tab (+ button or via the menu), but the tab opens without a title and never loads the shell (just a flashing cursor in the corner). I can move the tabs around in the window or pull a tab out of the window or put it back. All open tabs have flashing cursors, but none of them accept any input.

I can open the Settings dialog.

The red X and the menu Quit both do nothing (the application must be killed). If you click the X to close a tab, it asks if you are sure but never closes the tab (clicking the X a second time does nothing).

It seems to crash about the same time from one day to the next, yet the time of day does not appear to be a factor.

Approximate timestamps of crashes (for which I have kept record):

09-28 18:51 09-29 19:16 10-03 17:12 10-04 17:08 10:05 19:08 10-06 17:50 10-10 18:16 10-11 18:45 10-12 13:19 10-12 17:42 10-13 17:54 10-17 13:31 10-17 17:52 10-18 18:04 10-19 12:38 10-20 12:49 10-20 18:47 10-24 14:20 10-24 17:33 10-24 17:45 10-25 19:44 10-26 19:04 10-27 19:05 10-31 19:17 11-01 14:02 11-01 17:13 11-02 18:34 11-03 20:39 11-07 14:04 11-07 16:17 11-08 17:43 11-08 19:05 11-09 16:14 11-14 17:40 11-15 17:38 11-17 12:03 11-17 16:02

[felixse]

Sounds like something is killing the SystemTray process where the shell sessions are hosted. Maybe some anti virus software that considers this process suspicious (because it runs shells)?

[jamesisin]

I poked around Windows Defender (FT just crashed) and didn't see anything of interest. Looks like WD hasn't done anything except run updates, ever.

The tray object still existed after the crash. It stayed on a mouse-over (they will often disappear if an application has crashed). I was able to double-click the tray icon and this spawned a new FT window (which had a flashing cursor in the corner and was non-interactable as described previously).

Let me know if there is something specific you'd like me to check. It will crash again tomorrow. Around this time.

[jamesisin]

Here is the update to the list of crashes. I was gone for part of December so there is a gap and more recently it behaved for almost two weeks! I disabled the system tray object in case that was causing issues, but that may have made the crashing worse. Later I re-enabled it.

11-21 17:41 11-22 12:53 11-22 16:12 disabled system tray object 11-23 13:18 11-23 16:48 11-24 14:57 11-24 19:18 11-28 13:22 11-28 16:23 11-29 17:08 11-30 16:53 12-01 12:55 12-01 18:42 re-enabled system tray object 12-05 16:44 12-06 13:35 12-06 16:19 12-07 17:18 12-08 13:08 vacation 01-02 16:11 01-03 17:12 01-04 09:52 01-04 19:37 01-05 18:27 luxurious if mysterious period without crashes 01-16 18:20 01-17 12:59 01-17 16:35

[hanskokx]

While i appreciate your entusiasm, keeping track of the timestamps doesn't actually get us any closer to understanding why it's crashing. We're going to need logs, at the minimum, to track down whether issue is causing you to crash.

For what it's worth, i haven't had a crash at all on either system. — Hans Kokx On January 17, 2022 8:54:11 PM JamesIsIn @.***> wrote:

Here is the update to the list of crashes. I was gone for part of December so there is a gap and more recently it behaved for almost two weeks! I disabled the system tray object in case that was causing issues, but that may have made the crashing worse. Later I re-enabled it. 11-21 17:41 11-22 12:53 11-22 16:12 disabled system tray object 11-23 13:18 11-23 16:48 11-24 14:57 11-24 19:18 11-28 13:22 11-28 16:23 11-29 17:08 11-30 16:53 12-01 12:55 12-01 18:42 re-enabled system tray object 12-05 16:44 12-06 13:35 12-06 16:19 12-07 17:18 12-08 13:08 vacation 01-02 16:11 01-03 17:12 01-04 09:52 01-04 19:37 01-05 18:27 luxurious if mysterious period without crashes 01-16 18:20 01-17 12:59 01-17 16:35— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[jamesisin]

Give me something to check or do. I don't know how to help. This crashes for me every day.

[hanskokx]

I can tell you're frustrated. It's easy to walk away from software that frustrates you, so let me be the first to say thank you for helping make FluentTerminal better by sticking around.

The wiki has some information on logging. I'd start there, see what you can find, and report back anything of interest.

https://github.com/felixse/FluentTerminal/wiki/Logging — Hans Kokx On January 17, 2022 8:57:19 PM JamesIsIn @.***> wrote:

Give me something to check or do. I don't know how to help. This crashes for me every day. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[jamesisin]

Here are the log files. Let me know if I can do more.
Logs.zip

[hanskokx]

Tagging @felixse

[hanskokx]

Here are the log files. Let me know if I can do more.
Logs.zip

Thanks! I've tagged the author to peek at them. I'll try to take a look through them when i get a chance, too.

[jamesisin]

I changed logging to debug and relaunched both the app and the tray item, so if more logs are requested they will be logged as debugging.

[hanskokx]

By all means, if it crashes again, upload the logs. Those that you uploaded before didn't have much of anything in them. — Hans Kokx On January 17, 2022 9:20:29 PM JamesIsIn @.***> wrote:

I changed logging to debug and relaunched both the app and the tray item, so if more logs are requested they will be logged as debugging. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[jamesisin]

Just crashed. Here's the current log. fluentterminal.app20220118.log

[felixse]

Nothing interesting in this log. Can you maybe check Event Viewer Application Log (like here) as well? Look for the Error Event but also the next/previous 2-3 Information events as well.

[jamesisin]

Nothing whatsoever in the Application logs. fluentterminal.app20220206.log

[jamesisin]

Crashed again. Here is the updated log. fluentterminal.app20220206.log

[felixse]

Still nothing suspicious, sorry. I'm releasing a new version pretty soon, maybe this will help

[hkanakkan]

If a terminal window is open for some time idle, the same issue happens to me.. its just freezing like that..!! Had to force close the fluent terminal with task manager. To get continuous response, I was using "top" command sometimes this too even become un-responsive.

[jamesisin]

Looks like it's Win Defender's "App & browser control". Disable that and Fluent stays fluid indefinitely. I can find nothing in any logs which would inform any details though.