Overview
In the Nintendo Switch, when a command block comes into view, processing becomes heavy and an error occurs.

It's an error to just move around near a command block. we can't play properly.

I don't know if it's a bug, but if you can fix it, I'd like you to respond.

Details
≫ Model performance
Version:16.0.3
Remaining memory:16GB~
Minecraft total memory:1.0GB

≫ Minecraft setting
Video:Low quality/8-chunks display

≫ world
World type:super flat
World memory:3.0MB
Experimental element:OFF
Educational element:ON
Total command block:about 2900

We don't build anything as far away as possible, and I try not to go there.

About half of them use repeating command blocks and chain command blocks. But, it is turned off when not in use to reduce lag.

The content of the command block uses a lot of "/execute" and so on.

Error situation
If we stay away from the command block, we don't get any errors and fine. But when we get close to the command block and move around, we get an error.

Regardless of multiplayer, the error occurs even at the point of single play. When doing multiplayer, most people seem to get an error regardless of the host or participant.

Possible cause
There was a big specification change of the "/execute" from v1.19.50, but this problem occurred from v1.19.60. So we wondering if the problem is with the drawing of the command block, not the content of the command.

Or, because the experimental element is on, I think it may be affecting.

Steps to reproduce
If you want to reproduce similar behavior, put a bunch of command blocks in one place. Place at least 1000 command blocks. No need to go into repeat mode or run command blocks.

After that, please reproduce with the following steps.

≫ drawing issue
If nothing is entered in all command blocks…

Then, near the command block, check the move-around motion state.

If you can confirm the problem with this procedure, I think that the cause is in the drawing software.

≫ content issue
If enter any command in every command block…
(I think it's easier to check if you enter the "/execute" of v1.19.50 or later.)

Then, near the command block, check the move-around motion state.

If you can confirm the problem with this procedure, the cause is probably in the content processing of the command.

Lastly
This problem is not unique to me. I think it's pretty serious because it's also happening to other switch players…

If you can solve this problem, please fix it.
Sorry for the long sentence.

※The operation when displaying a large number of command blocks on the screen is considerably slower than before
※Experimenting in a new world will most likely not cause any errors. Therefore, I would like you to confirm ｢whether there is a possibility that the operation will be slower than before｣