You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "inbox@systemresearch.com (JIRA)" <ji...@apache.org> on 2017/03/05 18:32:33 UTC
[jira] [Issue Comment Deleted] (DOXIA-554) Parsing time for
Markdown documents can take very long and hang site generation
[ https://issues.apache.org/jira/browse/DOXIA-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
inbox@systemresearch.com updated DOXIA-554:
-------------------------------------------
Comment: was deleted
(was: " mirror https://github.com/vsch/maven-doxia <https://github.com/vsch/maven-doxia> which is version 1.7 only"
Maybe you were intending to type "1.6" instead?
)
> Parsing time for Markdown documents can take very long and hang site generation
> -------------------------------------------------------------------------------
>
> Key: DOXIA-554
> URL: https://issues.apache.org/jira/browse/DOXIA-554
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
> Affects Versions: 1.7
> Reporter: Michael Benz
> Attachments: maven-pom-sample-pegdown-performance.zip
>
>
> The parsing time for Markdown documents can take very long and hang site generation when e.g. long tables are being generated.
> The author of pegdown has marked the pegdown project deprecated since 2016-12-14 [pegdown.org|https://github.com/sirthias/pegdown/] and advises to switch to [flexmark-java|https://github.com/vsch/flexmark-java].
> {quote}
> The project is essentially unmaintained with tickets piling up and crucial bugs not being fixed.
> pegdown's parsing performance isn't great. In some cases of pathological input runtime can even become exponential, which means that the parser either appears to "hang" completely or abort processing after a time-out.
> {quote}
> Since the parsing timeout was increased in DOXIA-498 it is now possible to "hang" the site creation with a longer table like the one in this example.
> In case this sample is rendered using version 3.3 of the maven site
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)