during the development of CMS-14022 we got really awkward e2e tests failing. We could reproduce it locally as follows:

1. make changes in channel in CM
2. publish changes
3. After 2 go quickly to CM overview
4. Reopen from the CM overview the same channel

Then sometimes the CM just is an empty white page. No failing requests, no error logs in backend and no logs in frontend. Just nothing.

Reproduction

To reproduce it, it seemed possible by making the channel loading slow. This can be done by adding to

ChannelPropertyMapper#readChannel()

the following:

            try {
                Thread.sleep(250);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }

Note every channel and branch is delayed now 250 ms, so if you have many channels, lower the timeout.

With the above, after clicking publish, then quickly go the CM overview and reopen the channel, then the issue is reproducible.

In CMS-14022 in the end we 'fixed' it again by making the apparently expensive call

HstServices.getComponentManager().getContainerConfiguration().toProperties()

cheap again