"Wt: invalid ackId" for a certain setting.
On our complex web application, We have a use case thatoccasionally produces "Wt: invalid ackId" and freeze the client on some computer.
So, I created the isolated program that always produces the invalid ackId and attech it here. (main.cpp)
However, I do not confirm whether the isolated program could freeze the client or not.
The following are factors for invalid ackID
- It must have at least one setLayoutSizeAware(true) widget. Note that the WPaintedWidget uses setLayoutSizeAware(true) by default. And for our situation, it is not avoidable.
I am not sure if this is really a bug or just bad use case. In case that it is a bad use case, do you have any suggestion?
Workaround: using WebSocket solves the problem. But it is not an option for our case.
Updated by Apivan Tuntakurn about 2 years ago
Calling this as soon as possible solves invalid ackid.