Tasks are stuck when operating the account

[martin@rootjazz]

After the program was started, it ran several tweet publishing tasks. It was stuck for 28 minutes, and the log was: 65158

Had you turned on the debugging option as the logs do not contain the log files I need

[958]

It was turned on. Maybe it was turned off by mistake. Next time, I will upload the log and notify you.

[martin@rootjazz]

Can you check:

Tools >settings > debugging

if it is NOT checked, make sure it is checked. If it is checked, uncheck and check it again.


I can see in the logs when the delay happened. It was loading a single file from disk. But the log that tells me how that file was loaded, was not there.

[kiran]

This issue still persists. TD can not load accounts for actions after restarting software.

[martin@rootjazz]

This issue still persists. TD can not load accounts for actions after restarting software.

Please start a new thread about your issue.

Include as many details as you can. What exactly do you mean "can not load account for actions".
Do the accounts exist in the accounts list?
What does the the program display? What happens? Logs?

[958]

This time it lasted 3-4 minutes Log: 82372

[martin@rootjazz]

This time it lasted 3-4 minutes Log: 82372

Logs do not seem complete, they do not start early enough it seems. The logs start with the processor waiting for a lock that is in use.

09:31:49: GetDLD 8bda6a96-129e-4344-b686-ef663c078a4d_Follow want lockerDictDLD 49 RUN_NOW-b1fd32e6966e4d3f8dfe62f305bf92fd

09:34:35: GetDLD c1b4e532-742e-4c78-9900-948f3731a146_Follow released lockerDictDLD 50 no_thread_name

09:34:35: GetDLD 8bda6a96-129e-4344-b686-ef663c078a4d_Follow got lockerDictDLD 49 RUN_NOW-b1fd32e6966e4d3f8dfe62f305bf92fd

Thread 49 wants the lock and is waiting.
3 minutes later the lock is released by thread 50 - no_thread_name
Then we grab the lock and everything works.

The issue is before, what is 50 c1b4e532-742e-4c78-9900-948f3731a146_Follow doing with the lock for 3 minutes????

Looking at what is being loaded from disk, nothing happens until the thread 49 loads the file 8bda6a96-129e-4344-b686-ef663c078a4d_Follow

09:34:35: pre filelock: C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\database\DbLoggedData\8bda6a96-129e-4344-b686-ef663c078a4d_Follow.bin
09:34:35: got filelock: C:\Users\66\AppData\Roaming\rootjazz\Twitterdub\database\DbLoggedData\8bda6a96-129e-4344-b686-ef663c078a4d_Follow.bin

so the thread with the lock, doesn't load anything from disk according to your logs


I can only assume the issue started before you deleted your logs for the test! If you could clear your logs, restart the app, then repeat the test. The logs MUST have all the data then from when the app started, including where this lock / issue is being caused

[martin@rootjazz]

ok I've tested and test here and I cannot replicate your results. I need you to ensure you clear logs / add the config option *THEN* restart the app so the logs are complete.

The previous logs are missing the logs that would indicate (I hope) the issue



Regards,
Martin

[martin@rootjazz]

ok I think I may have an idea.

It's your stats loading (processed items in the last 24 hours)
You can disable this on app start via:

HELP > CONFIG > QUICK LOADING DO NOT LOAD STATS

This would be a no_thread_name type of thread that would access the lock we are waiting for


Check that option, restart the app and see if the problem still persists



Regards,
Martin

[958]

Sorry for the late reply, every time I start a new program, the task freezes. I just updated the program and it freezes after starting it.. Log: 48605. Three accounts were run, two of which were stuck for 12 minutes. One account was operated and run after the first two tasks ran for 6 minutes. The lag ended together. When the task was stuck, when switching to the account management function in the task running interface, the account disappeared and will not be restored until the lag ends. Is it a loading lag?