This test document is breaking joplin. Has something to do with the "Fenced code block" section.

[futuremotiondev]

Operating system

Windows

Joplin version

3.1.17

Desktop version info

Joplin 3.1.17 (prod, win32)

Client ID: 470c00f76de6488a98fd6a25df21fcda
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 3ea403d

Backup: 1.4.2
Csv Import: 1.0.1
Favorites: 1.3.2
Headings 4 to 6: 1.0.1
Insert Date: 1.0.1
Paste Special: 1.1.2
Table Formatter Plugin: 1.2.1

Current behaviour

1. Open this test jex document in Joplin: MD Test Document.zip
2. If Joplin doesn't go completely unresponsive, check the markdown source and look at the <pre> tag directly under the "Fenced" code block H3 heading.
3. See that Joplin injected a ton of backslashes followed by a final back-tick.
4. The original markdown source was this: https://gist.github.com/jonschlinkert/5854601#fenced-code-block

Expected behaviour

I expected Joplin to not insert massive amounts of backslashes into the document, even if the markdown was malformed.

I really do not know if what I supplied is sufficient to replicate the issue as I'm not sure when the corruption actually happened. But I suspect some kind of character escaping logic with code blocks isn't working right. It's also possible that an older version of the app broke the document and the bug no longer exists. I felt like reporting the issue anyway would be best as it might lead to some kind of bug fix.

Logs

No response

[futuremotiondev]

... that's not suspicious at all