cleaner.rb:76 : stack level too deep

[kidsil]

When trying to run jekyll serve I'm getting:

cleaner.rb:76:in 'caller': stack level too deep
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:76:in `parent_dirs'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:78:in `parent_dirs'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:78:in `parent_dirs'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:78:in `parent_dirs'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:78:in `parent_dirs'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:78:in `parent_dirs'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:78:in `parent_dirs'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/lib/jekyll/cleaner.rb:78:in `parent_dirs'
 ... 8179 levels...
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.5/lib/mercenary.rb:19:in `program'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.0/bin/jekyll:17:in `<top (required)>'
from C:/Ruby22/bin/jekyll:23:in `load'

When looking into line 76 (in cleaner.rb), I'm seeing
[parent_dir] + parent_dirs(parent_dir)

[shigeya]

Hi. Does this happen only if category archive plugin installed or not? I'm curious whether this relates to the plugin since the stack trace does not show anything related to it.

[kidsil]

Yeah, it happens *only *if the category archive plugin is installed

On Tue, Nov 10, 2015 at 11:10 PM, Shigeya Suzuki [email protected]
wrote:

Hi. Does this happen only if category archive plugin installed or not?
I'm curious whether this relates to the plugin since the stack trace does
not show anything related to it.

—
Reply to this email directly or view it on GitHub
#16 (comment)
.

[shigeya]

Okay, now I have tried with my test environment, but haven't case similar stack overflow. Would you please provide configuration detail?

[UnclePetros]

Hi, I have the same problem.
I've done a further analysis and found a possible cause of the problem on another jekyll plugin.
Have a look at this issue.

Thank you in advance for your work.