The page:

• voy:bn:আশি দিনে বিশ্বভ্রমণ

returns an "Internal error" when visited:

With parsoid disabled, it works: voy:bn:আশি দিনে বিশ্বভ্রমণ?useparsoid=0

Looks like someone is adding a stdclass as a parameter, which is then making replaceParameters crash because it expects an array of strings to strtr. The page uses Kartographer:

<mapframe text="Around the World in Eighty Days" width="900" height="280" latitude="33" longitude="8" align="right" zoom="2" show="listing">
{
    "type": "FeatureCollection",
...
}
</mapframe>

which triggers a strange-looking error in the legacy parser:

<div class="mw-kartographer-error">&lt;mapframe&gt;: JSON পার্স করা যায়নি: সিনট্যাক্স ত্রুটি</div>

There's this code in ParsoidTagHandler:

			foreach ( $errors[0]['params'] as $k => $p ) {
				if ( $p instanceof Message ) {
					$params[$k] = $p->toString( Message::FORMAT_PARSE );
				} else {
					$params[$k] = $p;
				}
			}

which was added in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Kartographer/+/1083876 to fix a CI issue. This crash is at a different place -- because the bad parameter seems to be an stdClass, we can actually serialize it just fine, it just blows up when we give it to Message to format. I'm actually not sure why the legacy parser doesn't die in the same way, but maybe serialization/deserialization isn't actually 100% faithful and we're looking at some object that serializes (to something that looks like a stdClass), but doesn't deserialize back to what it started as.

It's triggered by a JSON syntax error, which I fixed in https://bn.wikivoyage.org/w/index.php?title=%E0%A6%86%E0%A6%B6%E0%A6%BF_%E0%A6%A6%E0%A6%BF%E0%A6%A8%E0%A7%87_%E0%A6%AC%E0%A6%BF%E0%A6%B6%E0%A7%8D%E0%A6%AC%E0%A6%AD%E0%A7%8D%E0%A6%B0%E0%A6%AE%E0%A6%A3&diff=57136&oldid=55957

On my local debug machine, however, Parsoid handles this just fine, displaying "<mapframe>: Couldn't parse JSON: Syntax error" just like the legacy parser does.

I suspect this was actually bad parser cache contents generated by 1.43-<whatever> being deserialized by 1.44 which then crashed on it. Purging the cache seems to make this page work again, even for the old revisions with the bad JSON.