jekyll: Jekyll build --watch suddenly started to silently crash on windows

  • I believe this to be a bug, not a question about using Jekyll.
  • I updated to the latest Jekyll (or) if on GitHub Pages to the latest github-pages
  • I ran jekyll doctor to check my configuration
  • I read the CONTRIBUTION file at https://jekyllrb.com/docs/contributing/

  • I am on (or have tested on) Windows 10+

  • I was trying to build.

My Reproduction Steps

Run jekyll serve, or jekyll build --watch. These worked up until yesterday, and I am sure I did not edit the config or install anything new since then.

This may be related to #5462, and I have tried all the suggestions there, including the following:

  • updated from jekyll 3.3.1 to 3.5.1
  • ensured wdm gem is installed
  • ran gem clean and then bundle install
  • ran jekyll clean
  • moved project to a new folder and completely rebuilt
  • run commands as ‘bundle exec jekyll build --watch’
  • ran the commands with --safe, --trace and --verbose options
D:\Web\my_site> bundle exec jekyll build --watch
Configuration file: D:/Web/my_site/_config.yml
            Source: D:/Web/my_site
       Destination: D:/Web/my_site/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
                    done in 5.729 seconds.
 Auto-regeneration: enabled for 'D:/Web/my_site'

// then after around 5 seconds crashes to
D:\Web\my_site>

However, I did make a completely clean blog and build --watch works there. I’ll continue to work on this and report back if I find a solution.

The Output I Wanted

I’m finding it very hard to track down the issue here, as there are no errors logged. It may be that I’ve included something stupid in my site somewhere - but the real bug / issue is the lack of error reporting.

/cc @jekyll/build

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 16 (6 by maintainers)

Most upvoted comments

Awesome, thank you!

Ok, I’ll go ahead and close this. Thanks for the quick help guys! 😄

If the only change is an update to the OS, it sounds like that’s pretty clearly the smoking gun.

Have you reported the issue to the wdm folks? They may not have many people testing beta OS updates.