Failed processing Markdown document: Error while parsing action about idea-multimarkdown

[vsch]

The pegdown parser is iterative and can take too long trying to process markdown. This will happen on large blocks of text with unmatched inline markdown markers. The known suspects for this is the Quotes extension. If you have it enabled, try disabling it and see if the document will parse. I am even considering removing it as an option because of its tendency to timeout.

If the document that causes this is not proprietary, can you make it available to me for testing? I have been wanting to see if I can modify the pegdown parser so that it is faster in giving up trying to parse something that it cannot.

[bbrala]

I've uploaded all MD files in the project that failed to wetransfer. It pretty much node and php stuff. But only libraries of others.

http://we.tl/ouqXSJPkDY

[vsch]

Thanks. I am looking into it now.

[bbrala]

I've didn't have it later tho, so be carefull, maybe it was related to the .11 bug with the timing or something?

[vsch]

I hope you don't have all these directories marked as Sources Root. There are over 3800 markdown files there.

If the file is in a source root (not library source root) then the plugin will consider the file for link resolution annotations and completions. It will be slow to search through the list to pick out candidate files from very large lists. Unless you are making links to these files or actively working on them then there is no need to have them as source. Any file can be viewed, regardless of its source status.

I tried both enabling the directory as source root with all 3826 markdown files and it took a while for the idea to index everything and response time was the pits but nothing died. When I unmarked the directory as a source root everything looked good.

I suspect that it was a version 1.1.11 issue. There were a few things off in the indexing, since it was an early implementation. I still have to optimize handling of large file sets. I am not cacheing enough and clearing the cache unnecessarily but in the early stages of parser development I want to avoid stale cache issues more than slow performance.

Thank you for this mega load of markdown files. I'll use them for optimization testing. 👍