Tasks are stuck when operating the account

[958]

When verifying an account, the logging process gets stuck at the "Stats: Followers/followers: 0:3" step. The solution is to restart the program several times before it normalizes, or wait for the task to be stuck for dozens of minutes before it normalizes. Where does this happen? Is there a problem? Log: 68162

[martin@rootjazz]

Does this happen if you only run 1 action? Or does it require a certain usage for the issue to occur?

[martin@rootjazz]

goto

%appdata%\rootjazz\twitterdub\database\DbLoggedData\

find this file:
d9aba0c3-244c-46d2-9e54-eb01b61037ea_Follow

How big is it

If you cannot find it:
Order by file size

I guess it may be one of the bigger / largest files.

[958]

There is no that file in the DbLoggedData\ folder and the other files are only a few kb. This situation will also occur when sending tweets. The CPU load of the computer will also increase when the lag occurs. The lag mostly occurs when dub is just opened or the dub is reopened. It will appear later. New accounts will experience lag. Old accounts will not. When this happens, all the accounts on the account view page will disappear. When database 1 has this kind of lag, my other running data 2 will not be affected. I'm using a laptop and the cooling fan spins a little crazy when the task gets stuck. During the period when the task is stuck, 20% of the CPU load will be occupied until it returns to normal..Just now, an account got stuck after running the task of posting tweets for a few days. It was stuck for 18 minutes. Please check the account log of the last task: 47083

[martin@rootjazz]

Everything you report is indicative of the program trying to load a huge file. High CPU / long lag. Other programs / instances not effected. The program isnt' stuck, it's busy doing something that is just taking a long time.

This is what the logs indicate.

example:

10:00 load file (abc)....
10:18 loaded file (abc)...

There is no that file in the DbLoggedData\ folder and the other files are only a few kb.

Did you order by file size to view the biggest files? Can you double check, it's just everything is point to this being the cause and if it isn't, then I really do not have any idea. So lets just double check and confirm


I will check logs again

[martin@rootjazz]

It definitely looks like loading a processed log (dbloggeddata) issue.


Next update will log more specifically to confirm this

You will need to add a config:

HELP > CONFIG > ADD:
stats_debug

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html

Make sure you add the config, then repeat your action, it won't fix it. It will still take 15+ minutes.

Then submit logs afterwards and I should be able to tell you more about the issue

[958]

There is a computer task that lasted for 2 minutes, log: 53357. Another computer task lasted 19 minutes, log: 67718

[martin@rootjazz]

also what machine are you using? Home computer or VPS?
if VPS, is it a proper VPS or something like Amazon / azure? IF it is this, they are known to MASSIVELY throttle the CPU which can lead to very long times to load / process a file


checking logs...

[martin@rootjazz]

ok it's definitely that file, but it makes no sense as it reports it's empty


Please do this:

Add config:
HELP > CONFIG > ADD:
inmemory_debug

Restart app

Run the verify login action, then again submit logs and this should give me what I need



Regards,
Martin