It suddenly stops scraping, usually after 1500 to 3000 entries:
0.3.2 version introduced tab refresh feature which might have been the cause for the problems. 0.3.3 adds a timeout for tab refresh. In case tab refresh timeouts or the chrome tab fails a new scraper popup will be created.

It seems to take a lot more CPU. Once my computer sent me a warning while scraping (and not doing anything else):
0.3.x has optimized page load watcher which should make the data extractor start working immediately after the page has been loaded. This update makes the scraper scrape more pages per minute. Increased page scraping speed might slightly increase CPU usage. There shouldn't be any CPU overhead compared to previous versions. You can increase request interval to slow down the scraper.

It sometimes does not even start (not sure why)
If this still happens with 0.3.3 version can you please check whether any errors have happened in Web Scraper. Follow these steps to access error messages:

Open chrome://extensions/ or go to manage extensions

Enable “developer mode” at the top right

Open Web Scrapers “background page”

A new popup window should appear.

Go to “Console” tab. You should see Web Scraper log messages and errors there.