Markdown.ToHtml throws ArgumentOutOfRangeException #250

New Issue

claunia · 2026-01-29T14:31:45Z

claunia commented

2026-01-29 14:31:45 +00:00

Originally created by @Metalnem on GitHub (Dec 24, 2018).

Markdown.ToHtml throws an ArgumentOutOfRangeException when converting the markdown file from the attached archive. You can run the following code to reproduce it (the path variable should contain the path to the extracted file):

var text = File.ReadAllText(path);
var pipeline = new MarkdownPipelineBuilder().UseAdvancedExtensions().Build();
Markdown.ToHtml(text, pipeline);

Found via SharpFuzz.

Originally created by @Metalnem on GitHub (Dec 24, 2018). **Markdown.ToHtml** throws an **ArgumentOutOfRangeException** when converting the markdown file from the [attached archive]. You can run the following code to reproduce it (the **path** variable should contain the path to the extracted file): ```csharp var text = File.ReadAllText(path); var pipeline = new MarkdownPipelineBuilder().UseAdvancedExtensions().Build(); Markdown.ToHtml(text, pipeline); ``` Found via [SharpFuzz]. [attached archive]: https://github.com/lunet-io/markdig/files/2707155/ArgumentOutOfRangeException.zip [SharpFuzz]: https://github.com/Metalnem/sharpfuzz

claunia added the bug label 2026-01-29 14:31:45 +00:00

claunia closed this issue

2026-01-29 14:31:46 +00:00

claunia commented

2026-01-29 14:31:47 +00:00

@xoofx commented on GitHub (Dec 24, 2018):

Please stop reporting with an automated tool. I don't have time to download an archive and check the issues. So I prefer to have a simple code snippet with a reproducible error. Thank you

@xoofx commented on GitHub (Dec 24, 2018): Please stop reporting with an automated tool. I don't have time to download an archive and check the issues. So I prefer to have a simple code snippet with a reproducible error. Thank you

claunia commented

2026-01-29 14:31:49 +00:00

@xoofx commented on GitHub (Dec 28, 2018):

The issue should be fixed by commit 03858dc

I would appreciate if next time you can include the full exception directly in your report (to give more context).

Thanks for the fuzz testing. my apologize if I was angry when receiving these notifications but that was really a bad timing for me getting bombarded with issues while preparing Christmas diner 😅

The fact that the report looks like an automated stuffs was really scary for me at first, I thought I would receive hundred of them in the following minutes, hence blocking you straight.

@xoofx commented on GitHub (Dec 28, 2018): The issue should be fixed by commit 03858dc I would appreciate if next time you can include the full exception directly in your report (to give more context). Thanks for the fuzz testing. my apologize if I was angry when receiving these notifications but that was really a bad timing for me getting bombarded with issues while preparing Christmas diner 😅 The fact that the report looks like an automated stuffs was really scary for me at first, I thought I would receive hundred of them in the following minutes, hence blocking you straight.

claunia commented

2026-01-29 14:31:49 +00:00

@Metalnem commented on GitHub (Dec 28, 2018):

My bad about the missing stack trace! I started including them in reports for the other repositories the next day 😃

@Metalnem commented on GitHub (Dec 28, 2018): My bad about the missing stack trace! I started including them in reports for the other repositories the next day 😃

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/markdig#250