Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raising errors in callbacks crashes a Markdown instance #318

adamflorin opened this issue Oct 18, 2013 · 2 comments

Raising errors in callbacks crashes a Markdown instance #318

adamflorin opened this issue Oct 18, 2013 · 2 comments


Copy link

@adamflorin adamflorin commented Oct 18, 2013

Please see reproducible case:

If I use a Markdown instance repeatedly to render text, and raise an error within a custom formatting callback, eventually Redcarpet (or Sundown?) will crash, bringing down Ruby with it, with the error:

Assertion failed: (md->work_bufs[BUFFER_BLOCK].size == 0), function sd_markdown_render, file markdown.c, line 2544.
Abort trap: 6

In my case, I can just instantiate a new Redcarpet instance each time I render, so this is not pressing for me. But perhaps of interest to you?

lynxnathan added a commit to lynxnathan/grape-swagger that referenced this issue Sep 30, 2014
Copy link

@KCErb KCErb commented Apr 28, 2015


I get the same error by essentially this:

Attach my renderer somewhere accessible:

NameSpace.text_renderer =, opts)

Spin up an instance, and inside that instance call it again:

text_renderer.render text
  ### Inside TextRenderer
  def block_code(file_path, content)
    # . . .
    NameSpace.text_renderer.render content
    # . . .

I'll use @lynxnathan's suggestion of just making a new instance but thought I'd pass on another use case.

(In my case, I'm not using the fenced code block for code, I'm using it for a figure caption, and I want to be able to put bold text etc in the figure caption, thus I need to render inside as well).

Copy link

@aselder aselder commented May 18, 2016

We're seeing this also: RedCarpet 3.3.4, Ruby 2.2.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.