First of all, the new plugin is great.

Some days ago i noticed a major change in the build performance of my project (http://83.169.43.181/jenkins/job/HtmlUnit/). After some checking i found that this is because the parsing of the output takes really long.

19:43:09 [Java] Sleeping for 5 seconds due to JENKINS-32191...
19:43:14 [Java] Parsing console log (workspace: '/var/lib/jenkins/workspace/HtmlUnit')
19:59:59 [Java] Attaching ResultAction with ID 'java' to run 'HtmlUnit #262'.
19:59:59 [Java] Using reference build 'HtmlUnit #261' to compute new, fixed, and outstanding issues
19:59:59 [Java] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
19:59:59 [Java] No quality gates have been set - skipping
19:59:59 [Java] Health report is disabled - skipping
19:59:59 [Java] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)

Yes the log is really long, but this was not a problem in the past. With a bit more testing i found out that the log contains two really long lines with javascript inside. Looks like this lines are killing the parser.
Have attached the critical lines.

This is a log output for a fast run (one without the js lines nothing else changed).

22:37:19 [Java] Sleeping for 5 seconds due to JENKINS-32191...
22:37:24 [Java] Parsing console log (workspace: '/var/lib/jenkins/workspace/HtmlUnit')
22:37:24 [Java] Attaching ResultAction with ID 'java' to run 'HtmlUnit #263'.
22:37:24 [Java] Using reference build 'HtmlUnit #262' to compute new, fixed, and outstanding issues
22:37:24 [Java] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0
22:37:24 [Java] No quality gates have been set - skipping
22:37:24 [Java] Health report is disabled - skipping
22:37:24 [Java] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)

If you like i can provide the whole log also.