A lot of extra work was done to determine the number of taskvalues, on each call.
Sending 4 task values to a MQTT controller (C005) for example took 20 msec on average, now about 10 msec.
One often reported issue is that the ESPEasy node (especially ESP8266 ones) will crash when WiFi is unstable.
This could be due to memory suddenly filling up by the controller queue.
When creating a new item for the controller queue, there was no `(std::nothrow)` included on the `new` calls, so if running out of memory this might have thrown a `std::bad_alloc` exception, which are not caught and thus ESPEasy might crash on it.