Jump to content


There is a main process that has one thread and is connected to WBT API. Are there any limitations in case if this main one-threaded process is forked to created a child process and to connect to the same WBT API?

Share this post

Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Upon initialization, an object will initiate communication channels with the WBT Core firmware in the event that another WBT API class has not yet done so. Because these communication channels spawn additional threads, this will render all executables using the API "fork-unsafe" post the first instantiation of any WBT API Class.

To get around this issue, you may fork prior to the first instantiation of a WBT API class.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now