ZB failed to close and is still running in the background

[bomquay000]

Hi, I have recently upgraded to ZB Pro for trial and experience. After nearly a day of running ZB alongside ZPoster, I have encountered the following issues:

• Minor Glitches: There are some small bugs, such as occasional failures when creating or deleting profiles. However, I believe these are minor as they do not significantly impact the overall workflow.

There are two main issues that I believe require more attention:

1. Thread Limit Issue: I am only able to run 9 out of 10 concurrent threads. While the 10th thread is created successfully, it fails to launch. After encountering this error, I reduced the load to 7 threads and have not attempted to push it back to 10 yet.
2. Ghost Browser Processes: After running for a while, I noticed a case where ZB failed to close the browser, leaving it running as a background process. I attempted to close it manually, but the specific profile running in the background did not appear in the ZB control panel. My main concern is that if this happens frequently, it could lead to significant proxy data consumption if the processes continue to run undetected.

 

[Dmitriy_Zenno]

Hi, I have recently upgraded to ZB Pro for trial and experience. After nearly a day of running ZB alongside ZPoster, I have encountered the following issues:

• Minor Glitches: There are some small bugs, such as occasional failures when creating or deleting profiles. However, I believe these are minor as they do not significantly impact the overall workflow.

There are two main issues that I believe require more attention:

1. Thread Limit Issue: I am only able to run 9 out of 10 concurrent threads. While the 10th thread is created successfully, it fails to launch. After encountering this error, I reduced the load to 7 threads and have not attempted to push it back to 10 yet.
2. Ghost Browser Processes: After running for a while, I noticed a case where ZB failed to close the browser, leaving it running as a background process. I attempted to close it manually, but the specific profile running in the background did not appear in the ZB control panel. My main concern is that if this happens frequently, it could lead to significant proxy data consumption if the processes continue to run undetected.

View attachment 140912

Hello, regarding the 10-thread limit. There haven't been any complaints about this issue. Could you tell me if your templates are running too fast and can't launch 10 of the 10 threads?

Regarding thread freezing, this is a known issue. It's not the profile itself that's freezing, but the thread itself, so don't worry about the traffic. If this happens, the thread will stop automatically, but you'll need to wait 10-15 minutes.

To reduce this, I recommend adding the "Stop Instance" action to your templates (see screenshot for an example).

 

[bomquay000]

Hello, regarding the 10-thread limit. There haven't been any complaints about this issue. Could you tell me if your templates are running too fast and can't launch 10 of the 10 threads?

Regarding thread freezing, this is a known issue. It's not the profile itself that's freezing, but the thread itself, so don't worry about the traffic. If this happens, the thread will stop automatically, but you'll need to wait 10-15 minutes.

To reduce this, I recommend adding the "Stop Instance" action to your templates (see screenshot for an example).

View attachment 140913

-Regarding the 10-thread issue, I'll check it later as it's not a priority for me right now.
-As for the frozen threads: my workflow already includes 'stop profile' and 'delete profile' blocks (since my tasks require creating short-term profiles and deleting them afterward). It’s been 6 hours, but the frozen threads are still there.
I think restarting ZB would resolve the issue, but since my automation is currently running, I don't want to stop it for a deeper investigation right now. Regardless, I believe this is a technical bug that needs to be addressed

 

[Dmitriy_Zenno]

-Regarding the 10-thread issue, I'll check it later as it's not a priority for me right now.
-As for the frozen threads: my workflow already includes 'stop profile' and 'delete profile' blocks (since my tasks require creating short-term profiles and deleting them afterward). It’s been 6 hours, but the frozen threads are still there.
I think restarting ZB would resolve the issue, but since my automation is currently running, I don't want to stop it for a deeper investigation right now. Regardless, I believe this is a technical bug that needs to be addressed

I completely agree with you.
We're in the process of resolving the issue with threads freezing.

 

[bomquay000]

I completely agree with you.
We're in the process of resolving the issue with threads freezing.

The error I'm encountering seems more serious than I thought. I restarted ZB and ZPoster, but the frozen threads still haven't been released (one frozen thread from hours ago that I mentioned, followed by another one just now).
I even tried restarting my computer, but those two frozen threads are still stuck. This is honestly quite confusing to me.

 

[bomquay000]

After restarting the computer and leaving ZB running for about 10 minutes, the two frozen threads were finally released. I’m going to adjust my project by slowing down the create, stop, and delete operations to see how it goes

 

[bomquay000]

By the way, I’d like to know: where can I find the folder that stores the profiles on my local machine? I've been searching for it everywhere but still can't find it. Thanks!

 

[Dmitriy_Zenno]

By the way, I’d like to know: where can I find the folder that stores the profiles on my local machine? I've been searching for it everywhere but still can't find it. Thanks!

Path to profiles C:\Users\{USER}\AppData\Local\ZennoLab\Profiles

 

[bomquay000]

Path to profiles C:\Users\{USER}\AppData\Local\ZennoLab\Profiles

I absolutely love today's new update!!! All the bugs with creating, running, and—most importantly—stopping profiles are now working smoothly without any issues. I also noticed that CPU usage has dropped by 50%. I’m currently running a project with 50 threads, and everything is rock solid

 

[Dmitriy_Zenno]

I absolutely love today's new update!!! All the bugs with creating, running, and—most importantly—stopping profiles are now working smoothly without any issues. I also noticed that CPU usage has dropped by 50%. I’m currently running a project with 50 threads, and everything is rock solid

Great, I'm really glad you're doing well.

 

[bomquay000]

Great, I'm really glad you're doing well.

In recent days, I have been experiencing significant issues connecting to the ZB server. The connection is occasionally interrupted briefly, but often remains disconnected for long periods. During these times, ZPoster fails to function. I have to reinstall ZB to restore normal operation, and this has persisted for three consecutive days.

Please check your servers. This connectivity issue also appears to be the main reason why ZPoster cannot stop or delete ZB profiles; when the connection is lost, ZPoster is unable to interact with ZB at all.
To clarify, my internet connection is perfectly stable. I can also launch ZPoster without any issues. However, ZB itself fails to open, and the reinstallation process even freezes.

 

[Dmitriy_Zenno]

In recent days, I have been experiencing significant issues connecting to the ZB server. The connection is occasionally interrupted briefly, but often remains disconnected for long periods. During these times, ZPoster fails to function. I have to reinstall ZB to restore normal operation, and this has persisted for three consecutive days.

Please check your servers. This connectivity issue also appears to be the main reason why ZPoster cannot stop or delete ZB profiles; when the connection is lost, ZPoster is unable to interact with ZB at all.
To clarify, my internet connection is perfectly stable. I can also launch ZPoster without any issues. However, ZB itself fails to open, and the reinstallation process even freezes.

Hello, I wrote you a private message.