Cronmaster (1.5.3) UI Lockup with logging enabled and long running job

[ShadowTox]

I tested 1.5.3 with a logging enabled and a long running job. Two different scenarios:

1. Very long job, created a log file: 13,416 KB in size with 98,860 lines.
   I submitted the job and the Live Job Execution screen showed. I let if display for about 1800 lines and then clicked the x to close the window, the cronmaster UI showed as normal. after some time, it became unresponsive (locked up). I restarted the docker container, went back into Cronmaster and i could view items but not edit any scripts, and eventually the UI (view only) locked up. this repeated until the job finished creating the log. even when the job was finished the UI was still locked up. final restart of docker and all was good.

2. Long job, created a log file: 6,178KB in size with 48,405 lines
   I submitted a second job that was long but not like the first. I also left the Live view on screen the entirety of the job run. it scrolled through the new log entries as it should and eventually a warning came on the top of the screen, Warning large log file, showing last 5000 lines (or something like that. i moved the window and the warning disappeared), but the log kept displaying new log entries as the job ran. somewhere around 25,000 log entries the UI seemed to lock up but, after a long pause started showing new log entries. the pause was longer than expected because it was 'temporarily locked up' on a small png file. the live view didn't catch up with the actual log however and displayed behavior of locking up periodically. eventually the browser gave a blank screen with the following error. Application error: a client-side exception has occurred. the job eventually finished, i restarted the docker container and cronmaster UI acted normal.

My general thoughts on this: having the ability to enable and view historical logs (even when the job is running) is the most important and valuable part of this change. if solving the Live-view feature is too difficult then maybe you just modify it but still enable going to view logs and seeing the log contents of the active job. The live is most important on new jobs to get a sense if they are starting up in a good fashion. Maybe the following would be a good workaround if possible: add a new check box - 'display live view', still have the 'Enable Logging' check box. then with the live view only display the first 100 or 200 lines and then 'disconnect' the actual log being generated from the live view while still showing the live view so we can review the startup entries for any issues. and then finally click the 'x' to close the live view. of course the perfect world feature would be able to periodically open up the log for the active job and have a 'live-view' effect of new entries showing, but i think you can add this part at the end of your long list of to-do's for this great program since this would just be the final icing on the cake. (sorry for the long entry but i want to give you as much as i found to help if i can)

[ShadowTox]

one more request, please add the version number on the main screen so we can easily see what version is being run :)

[fccview]

one more request, please add the version number on the main screen so we can easily see what version is being run :)

Hey, version number is on the login screen, may need to add it somewhere else too, but at least you do have a place you can check it!

I really hoped the fix I did for this worked, I can't really test it safely, i may need to have an infinite loop script just to test this as i'm kinda working blind otherwise 😆

I may need to revert back to the previous version of the live view (before my fix i did for you) and work from there, i'll try to virtualise the scrolling so it just adds new lines as you scroll rather than keep the full log in view, it's a trial and error situation unless I can realistically replicate your crazy big log file lol

[ShadowTox]

i knew i saw the version somewhere, but couldn't find it after i logged in...lol
since you added the live view it's always locked the UI. so if it is too big of an issue to fix it, i would say just remove the live view and still maintain the logging you added. btw, my huge logs files are just copying lots of files and folders. all very small but very large in number. problem is it takes a very long time so once i submit a job there is a long delay until i can redo it. thx again for you work on this!

[fccview]

Sooooo I made a script that randomly generates 15k lines and played around with it a bit.
I think the best solution I could find was to give the user the option to see the last N lines and at YOUR own risk show the full log

something like this.
I'll push to develop soon and it'd be great if you could try this ❤️

I'll let you know

[fccview]

Hey this is on :develop.
Please let me know if it's improved at all for you!!

[ShadowTox]

Great! I will test it tonight

…

________________________________ From: fccview ***@***.***> Sent: Thursday, November 20, 2025 12:13 PM To: fccview/cronmaster ***@***.***> Cc: Dennis ***@***.***>; Author ***@***.***> Subject: Re: [fccview/cronmaster] Cronmaster (1.5.3) UI Lockup with logging enabled and long running job (Issue #67) [https://avatars.githubusercontent.com/u/112867047?s=20&v=4]fccview left a comment (fccview/cronmaster#67)<#67 (comment)> Hey this is on :develop. Please let me know if it's improved at all for you!! — Reply to this email directly, view it on GitHub<#67 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEILSEO2UNVD3QXY6AKQHT35YHGVAVCNFSM6AAAAACMWPHO6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJZGYZTQOBVGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ShadowTox]

installed the develop version. ran a test job that generated 33215 log lines. i left the live view on the screen and changed the log lines to display from 100 to 1000. and eventually set it to 100. it all acted as expected. while set to 100 i let the job run. at line 24,673 the live view stopped updating new log lines. the job was still running to completion. the 'running' circle on the live view was still visible after the job finished. I clicked the 'x' and it closed, but then the browser session crashed and gave me a white screen with application error. However, i was able to open another browser session and get back into cronmaster.

while the job was running (and both before and after the live view froze up. i opened another session of cronmaster and was able to do everything fine. So basically the changes you made are good to limit the lines and that all worked. And you also fixed the issue when the live view locked up which then took down the entire program forcing me to restart the docker container. i didn't have to do any of that and it is still running fine...YEA!!! as far as i can tell the only remaining bug is that the live view stopped updated at line 24,673. btw i ran two jobs, both locked up, but i think that the line number was much higher on the first one, but didn't record that. i have a suspicion that the reason it stopped updating was because the job finished, i will run 1 more test and watch that timing and let you know.

[ShadowTox]

just ran a third job. the live view stopped updating at around 18,000. it was the same job and it finished normally. but the job was still running when the live view locked up. i didn't touch the browser and after the job was finished, the browser session crashed with the following error (note: it is the same error all the time):

Application error: a client-side exception has occurred (see the browser console for more information).

so I am not sure but I am always able to get back into the program w/o restarding the docker

[ShadowTox]

Hi, i ran the job again after a reboot of my windows 11 machine. at line 21,163 the live view locked up. I had another cronmaster session active and was looking at the log list of another job, and when the live view locked up (first session), the 2nd session seemed to hang (non-responsive). the first job crashed with application error as it has before and when it crashed the 2nd session seemed to release and cronmaster responded. the job completed normally. the line the live view locks up doesn't seem to be consistent, but it is consistent with crashing that session, but not affecting the rest of the cronmaster docker.

[fccview]

Hi, i ran the job again after a reboot of my windows 11 machine. at line 21,163 the live view locked up. I had another cronmaster session active and was looking at the log list of another job, and when the live view locked up (first session), the 2nd session seemed to hang (non-responsive). the first job crashed with application error as it has before and when it crashed the 2nd session seemed to release and cronmaster responded. the job completed normally. the line the live view locks up doesn't seem to be consistent, but it is consistent with crashing that session, but not affecting the rest of the cronmaster docker.

Just to be clear, this happens while you have only 100/500 lines visible or are you clicking to "view full logs"?

Because clicking on "view full logs" WILL lock up your session as your client can't handle that much data stream at once. The fix was to only show a few lines at the time, you can check the full log from the history once the job is finished of course.

Let me know

[ShadowTox]

This was with 100 lines and then I tried again showing 500 lines, and both locked up. I never clicked the view logs.

…

________________________________ From: fccview ***@***.***> Sent: Friday, November 21, 2025 11:58 PM To: fccview/cronmaster ***@***.***> Cc: Dennis ***@***.***>; Author ***@***.***> Subject: Re: [fccview/cronmaster] Cronmaster (1.5.3) UI Lockup with logging enabled and long running job (Issue #67) [https://avatars.githubusercontent.com/u/112867047?s=20&v=4]fccview left a comment (fccview/cronmaster#67)<#67 (comment)> Hi, i ran the job again after a reboot of my windows 11 machine. at line 21,163 the live view locked up. I had another cronmaster session active and was looking at the log list of another job, and when the live view locked up (first session), the 2nd session seemed to hang (non-responsive). the first job crashed with application error as it has before and when it crashed the 2nd session seemed to release and cronmaster responded. the job completed normally. the line the live view locks up doesn't seem to be consistent, but it is consistent with crashing that session, but not affecting the rest of the cronmaster docker. Just to be clear, this happens while you have only 100/500 lines visible or are you clicking to "view full logs"? Because clicking on "view full logs" WILL lock up your session as your client can't handle that much data stream at once. The fix was to only show a few lines at the time, you can check the full log from the history once the job is finished of course. Let me know — Reply to this email directly, view it on GitHub<#67 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEILSCVY4GREZLELMPQ3LT36ACSRAVCNFSM6AAAAACMWPHO6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRVHA3TGNBVHE>. You are receiving this because you authored the thread.Message ID: ***@***.***>