Community Application tends to go unresponsive a lot.

What is your deployment? I noticed from an earlier screenshot you had two system notifications, one of which was mentioning that the fallback Database Message Bus is enabled. This is an inherently low-performance fallback, and should be substituted for the Socket Message Bus Server or another bus. But the fact that it was enabled makes me curious about the rest of the deployment as well.

Additionally, do you have WebSocket enabled on your web server? Community will try to use the best available transport: WebSocket, EventSource, or long polling.

I skipped the installation of the Socket Bus during the installation. Could that be the reason?

This is a required component of the installation. As is the Job Server in case that was skipped as well.

Ok, thanks. I will install it now. I've installed the job server.

There could still definitely be other issues too. If so, I'd still interested in what your deployment looks like, and whether you have websockets enabled on your server.

Also if it continues, I'd recommend checking the Exception and Event logs under Administration > Monitoring. Make sure something isn't erroring, or that the app nodes aren't constantly restarting, or something else unusual.

Is Socket Message Bus Service supposed to be enabled under Admin > Site? I am not allowed enable it at the same time as Database Message Bus.

That's correct. Only one bus can be enabled at a time.

That's correct. Only one bus can be enabled at a time.

The application has crashed my development computer again. When I look in the exception log I can see a message - 'Socket Message Bus Service Unavailable' and 'EndpointNotFoundException: Could not connect to net.tcp://localhost:9623/bus. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:9623.'

IbrahimK said:

The application has crashed my development computer again.

Yikes, crashed your computer? What do you mean?

As for the exception, it would indicate most likely that the message bus server is not running.

It froze my computer for about half an hour.

I'd love some more details and steps to reproduce this. This is certainly not a known or expected outcome for any exception.