neo4295 wrote: ↑Mon Mar 31, 2025 11:51 am
Since updating to 3.745 I too have had TD shut down at some point.
This phenomenon is similar to what happened a while ago when TD was shutting down.
I think something changed in 3.745 is affecting it because 3.744 does not cause the shutdown.
same for you? right click > cancel?
1:TD doesn't show which account is blocked, I do verification of all accounts, and I see that there are a lot of blocked ones.
2: The TD closes when I press right click>cancel action
Checked the code, right click > cancel cannot crash and kill the app. Any errors would be detected and displayed to you in a popup.
IS it every time?
Only certain actions?
Only certain actions at certain times?
Seems is it every time
action Follow share accross acounts
the program closes not only when I press cancel, the program closes during work (follow or like > share accross accounts), that's why I say that this happens because of banned accounts that are not shown in Accounts Tab
ok exported banned account(s) would be very useful and the logs after shutdown without restarting
There are not errors in the logs, nothing to indicate the program crashed and closed. It's as if the program is just killed by the OS. Can you check even log / event viewer to see if there is anything there to indicate the OS killed the process
IF the AV / app security killed the app it should be logged.
I've also noticed you get a LOT of timeouts trying to get user_Details / tweet_detail. I've increased the timeout and made it a custom value so in a future update you will have a greater control on the various timeout types.
It happens on all 4 computers, but only with the version of 3.7.4.5
I rolled back a 3.7.4.4 on one comoutrr and it's working fine.
On another computer, where I'm sure there are no banned accounts, the 3.7.4.5 version works great.
On the 3 computers where I put FOLLOU separately (not shared accross account), it also works great.
I'm already sure
I found the account that has SUSSPENDED (he tries to make FOLLOW for a long time, but he can't, and he doesn't stop) , I right-clicked on its process > cancel action, and TD closed
size of this account's log file 11591
I sent you a new zip log to your email
Account : Marie0339665614
definitely seems like TD is the cause, but within an action, it cannot crash the app, it's self contained within an action and any crashes are handled.
The main app can crash the app, but the right click CANCEL routine cannot as that is already in a self contained instance to handle any potential crashes.
Let me check logs again, I must be missing something
ok, I can see something looping, you keep receiving a 401 response as "cannot authenticate" and there is a cloudfare header. But there are still no TD logs that the program crashed itself, it is as if something external killed it (which the OS maybe did for the loop hitting the same page...
well it seem the ct0_fix didn't help at all, so I Will remove that test. so that should help.
