Michael Cotterell

Retested on 1.20.10,

the issue appears to be resolved, killing a single captain, no second raid occurred.

can anyone else please verify the same result?

thanks.

my test on Survival, Hard, Standard raid farm design (silents older large water trap not small box trap version), shows after killing ONE Captain, turning off lower trident killer so no more captains are killed. then climbing up to the afk I triggered the raid as normal, after successfully completing the raid I received the hero of the village as expected.

without moving from the afk, a short time after another raid is then automatically triggered,

once this raid is successfully completed hero of the village is then refreshed,

no further raids are triggered,

M.

my test on Survival, Hard, Standard raid farm design (large water trap not small box trap version), shows after killing ONE Captain, turning off lower trident killer so no more captains are killed. then climbing up to the afk I triggered the raid as normal, after successfully completing the raid I received the hero of the village as expected.

without moving from the afk, a short time after another raid is then automatically triggered,

once this raid is successfully completed hero of the village is then refreshed,

no further raids are triggered,

so i would suggest that triggering the second raid is the real issue, as per ticket MCPE-167246.

M.

I would like to confirm the same issues as reported on this thread, cant add anything much different to help except my situation is Windows 10, i5 7400 @ 3.00 Running BDS versions 1.17.32 has the same issue, upgraded to 1.717.33 and still have the same RAM issue,

when launching the world it almost instantly consumed 14/15gb of  my 16gb RAM just opening the world with BDS, it takes some 10 minutes to complete the server launch at which point RAM fluctuates back to about 9-11gb. while logging into the world to play the RAM increase back to 14/15gb.  then settle back to 9-11gb.  while in the game loading new chunks takes several minutes and again RAM continues to max out and idle back to about 75% load. chests taken about 30 seconds to register opening if at all, blocks can take up to a minute to break etc or then not.

Text chat is delayed by several minutes, and text is often grouped not back n forth.

Exiting BDS console using STOP takes forever, even longer than the original loading, then the RAM count drops steadily down to less than 1gb over about 15 minutes, twice from about five or six times i had run some tests I then heard my PC noise pitch change suddenly and the RAM just climbs back up to 11gb, it seem like as it was about to close it looped back to running again. this hasn't happened every time but was odd seeing it at all.

 6 Oct 2021 mojoang released 1.17.34.02 - I can confirm the RAM issue persist in this version update.