Can confirm it affects the latest update. Mostly appears when there is a lot of screen action, explosions and many mobs. But we also encounter it situations when there is really nothing going on. Soggy Swamp caused the most for us, it was almost reproducable.
Edit: can also confirm that the workaround with going into sleep by holding the home button fixes this in some cases.
Just to add a few comments, since this is finally getting hot:
I think this is was the most commented/voted bug for the Switch and since I experienced this bug/limitation myself I can clearly say that it is not fully 'resolved'.
I do recommend reading the developer/moderator response who just switched the status. The crashes are reported and worked on internally. While we all wish for a more transparent view on what is going on, Mojang clearly does not want to share that with us. It might open up legal issues and I'm fine with that.
Having said that, I think the response could have been worded a bit better so I'm with @HalfScoper here to chill a bit. I was also hoping for a "we are working on this" kind of response. But this is a Bug-Tracker so if they want a reproducible bug, then that is fine. It's probably even in the requirements for opening a bug anyways.
But I also think that it is expected to have a bug-free product even if we are playing on a switch. My Switch is also overclocked thanks to open-source and while it's almost on fire while playing MCD, it is not a "fluent" experience all the time. I managed to play through it (4 player local co-op) nonetheless.
Also last I head MCD is not OpenSource so we cannot really "contribute fixes".. cause ya know.. we payed money for this and a bug tracker is all they got.
Thanks to the devs (really!) for kinda working on this and looking at this bug. But not everyone here is a developer, so expecting a 100% reproducible instruction-set seems overkill and I feel like enough players signed up here to tell you that there is indeed an issue. Special Thanks to the guy who provided the workaround; that really worked 99% of the time.
Edit: Also thanks to @Arden, you have been like a static heartbeat to this bug with all your edits and I appreciate all the details you've given.
Can confirm it affects the latest update. Mostly appears when there is a lot of screen action, explosions and many mobs. But we also encounter it situations when there is really nothing going on. Soggy Swamp caused the most for us, it was almost reproducable.
Edit: can also confirm that the workaround with going into sleep by holding the home button fixes this in some cases.
Just to add a few comments, since this is finally getting hot:
iswas the most commented/voted bug for the Switch and since I experienced this bug/limitation myself I can clearly say that it is not fully 'resolved'.Thanks to the devs (really!) for kinda working on this and looking at this bug. But not everyone here is a developer, so expecting a 100% reproducible instruction-set seems overkill and I feel like enough players signed up here to tell you that there is indeed an issue. Special Thanks to the guy who provided the workaround; that really worked 99% of the time.
Edit: Also thanks to @Arden, you have been like a static heartbeat to this bug with all your edits and I appreciate all the details you've given.