I checked the raw response from the server. The comment is not triple back ticked. It is only single back ticked. In the original instance it is triple back ticked. This is likely a syncing error between instances. Eg. the user posted the comment with single back ticks in the original instance then corrected the comment however the 2nd instance only received the original comment and not the correction.
I think markdown technically doesn't define what the correct behavior is here so the behavior by the client isn't "wrong" however it's unexpected. I will issue a fix so that the markdown parsing is consistent with web. Eg. if an inline code block contains new lines, the new line characters are converted into spaces.