Problem

The Search/Replace function may runs into timeouts with larger tasks and the "replace all" functionality and replacing more than ~20 occurances.

First more details about the problem are needed:

• how is search/replaced implemented in the backend ?
• can we speed it up ?
• is an async operation needed in the frontend ?

Solution

An async operation is very likely needed.

• This should be done in a worker
• All segments, that are loaded already in the UI and where something will be replaced should be locked
• All segments in the back-end where something will be replaced should be locked
• When replace is done, UI is notified via messagebus, that segments are unlocked.