Poor performance with large amounts of text about micromark-extension-gfm

[github-actions]

Hi! Thanks for taking the time to contribute!

Because we treat issues as our backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn’t an exact duplicate but is closely related.

Thanks,
— bb

[ChristianMurphy]

Duplicate of remarkjs/remark#978

To quote that discussion:

Hey! GFM tables are tough to parse, they are different than other markdown constructs and require looking ahead further.
That being said, there are likely things to improve where they are parsed: https://github.com/micromark/micromark-extension-gfm-table. Perhaps you can profile and help there?

You can for example try different versions of micromark-extension-gfm-table and micromark to understand if this is something that was introduced at some point or if it was already present from the start.
You can also try different markdown input, to see if the problem might be lines or columns or long cells or what.
You can change states to switch to the nok state, to see if that magically solves everything (of course, nok stops parsing, so it also breaks everything).

You can read in particular the Architecture section in the micromark readme for more on how the project works.

source: remarkjs/remark#978 (comment)

[github-actions]

Hi team! It seems this post is a duplicate, but hasn’t been marked as such. Please post a comment w/ Duplicate of #123(no final .) to do so. See GH docs for more info.

Thanks,
— bb