Closed dneuge closed 3 years ago
HTML component was updated directly before, now all HTML changes are aggregated and component (including getters) is only interacted with if there is new log content to be added.
This also solves #8 as there already is a hard rate limiting at 200ms intervals which was only broken by to many component interactions; this fix should also mitigate the previous race condition.
To reproduce generate plenty of messages in short time, i.e. by enabling trace-level logging. Since messages are appended one-by-one, HTML component is lagging by a lot. This also increases chances to hit #8.