We don't have a known limit on number of files or file size, but Node.js itself does.
>From what I've read, the most likely cause is a single large file. Do you have any files that are larger than a megabyte or two? Are there any other statistics you can share about your project folder? Number of subdirectories or files? On Fri, Jan 23, 2015 at 9:57 AM, Jim Gourgoutis <[email protected]> wrote: > It's this same issue. https://github.com/eslint/eslint/issues/957 FWIW > I'm running v0.12.0 on an 8 core Linux box with 64G of memory. > > Thanks, > -Jim G > > > > On Friday, January 23, 2015 at 9:54:20 AM UTC-8, Jim Gourgoutis wrote: >> >> When I throw ESLint at a large project folder, I'm getting "FATAL ERROR: >> CALL_AND_RETRY_2 Allocation failed - process out of memory" errors. Does >> ESLint have a maximum number of files/errors it can handle? >> >> Thanks, >> -Jim G >> >> -- > You received this message because you are subscribed to the Google Groups > "ESLint" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- ______________________________ Nicholas C. Zakas @slicknet Author, Professional JavaScript for Web Developers Buy it at Amazon.com: http://www.amazon.com/Professional-JavaScript-Developers-Nicholas-Zakas/dp/1118026691/ref=sr_1_3 -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
