ZP v. 5.2.1.0 - keeps freezing

[shabbysquire]

In v. 5.2.1.0, when I'm running more than 1 thread for about 15 minutes, ZP just stops. I have to stop and restart all the time.

 

[rostonix]

Maybe problem is logic of your project. If you use internal loops without restarting of instance.

 

[shabbysquire]

The template doesn't use internal loops, it's all open ended and I execute once only. I'm not really sure what's going on, tbh.

 

[rostonix]

And what it does for 15 mnins if you dont have internal loops?

 

[shabbysquire]

The error? If one thread is running, all is ok. But more than one and everything freezes. I checked CPU/memory, but that seems ok.

It was worse when I used keystroke emulation for logging in, but it improved slightly with Set Value in fields. It might not be that though.

Btw, the version is: 5.1.2.0 (not 5.2.1.0). I'll probably upgrade to v. 5.3 soon, so I might be ok.

 

[shabbysquire]

Keep happening again. There's no errors/warnings in the log. Always with more than one thread.

 

[shabbysquire]

Ok, updated to latest v 5.3.1.0.

It ran ok for 1-hour, now it's doing the same. I ran a maximum of three threads, then it just freezes. Can anyone give some advice?

Thanks.

 

[rostonix]

Record screencast which will show this + include in screencast info about task manager + system's resources

 

[shabbysquire]

Will do. But in the meantime, are there settings that I might have overlooked, or common issues (like firewall) that might cause this?

 

[rostonix]

This is not common issue by itself)

 

[shabbysquire]

Record screencast which will show this + include in screencast info about task manager + system's resources

Re latest version: 5.3.1.0.

I have included screencast

Important parts of video:

2:00 all threads become 'stuck', and won't end;

2:18 I have to cancel base.exe * 32 (FFInstance) in task manager.

Note: in task manager > processes, there are usually 2 x FFInstance running at once. Is this normal?

 

[shabbysquire]

Well, managed to get it sorted out!

I tried nearly everything: adjust CPU (set affinity), run as admin, tried various compatibility modes, installed in new environment, and a load of other shite, but the problem persisted. So I played around with the template by removing a few actions. Now it seems to work ok.

At least now I don't have to babysit the ruddy thing!

 

[rostonix]

Hello mate sorry for delay with answer, was outside the city for weekends)
Any hint what exactly you changed?

 

[shabbysquire]

Hello mate sorry for delay with answer, was outside the city for weekends)
Any hint what exactly you changed?

I've attached a pic below. The actions circled in red is how I set it up before (this caused threads to freeze).

The template used to have 4 x possible endings, but now only 3. You see see the previous actions I used in the pic. Also, the original setup did the same in v. 5.1.2.0. and the newest version.

Thankfully, it now works like a charm - and the other part doesn't really matter.

 

[shabbysquire]

I think it might be the Picture action. The template above was running for months ok, but when I added picture > disable, all the threads kept on 'sticking' (i.e. won't start properly, or reach the end of thread and do nothing). I had to keep ending the base.exe*32 in task manager every 5 - 10 mins!

Then I started using an old template without picture action, and it's running without any issues.

 

[rostonix]

I saw it once on 1 site. Scripts didnt work properly with disabled images.

 

[shabbysquire]

I saw it once on 1 site. Scripts didnt work properly with disabled images.

Thanks Rostonix. I'll try to recreate the issue with current one that is working ok. If it is disable picture, then I suspect deleting the (bad) action might restore the template.

 

[shabbysquire]

The bug is back in latest ver. It always happens with picture enabled, and when running more than one thread. Half of all threads just 'lock up (just stuck).

 

[rostonix]

Record screencast and show what you mean exactly + info aboout task manager, how much resiurces are avialable