-
Notifications
You must be signed in to change notification settings - Fork 161
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
Java Heap Space limiting more than 50ish title searchs #329
Comments
I never did such big scraping session.
To rule out the first one can you do the following checks: In the terminal you start type the command line in, you should see something like: Also can you try adding -Xms2048m -Xmx4096m to your command line. If this does not help, i will profile application's memory usage when i got some time |
@Wizell Unforunately I use windows and do not code. So i have no way of knowing how to do those you mentioned. |
How do you start JavMovieScraper jar file ? |
I have Java runtime environment 8 installed. On Windows, I just double click on the .jar. It default to launch with JRE |
If i try to run it cmd in windows, I get this big box error:
|
You got the command line right, the error is a mistake in the settings of the application. |
Thanks @Wizell I was able to run the command on a VM that runs my primary scraping. I could only max it to 1gb heap and free mem. I'll try to see if it can do more than 50 titles. I typically scrape 100 titles every 3-4 days. |
@Wizell Do you have a quick idea how to compile your files from github into a working .jar? Maybe for future users because we see code fixes but unable to use them until a release. |
java -jar JAVMovieScraper-v0.3.7.jar |
Issue: When I use JAVMovieScraper to scrape for anything more than 50 titles, sometimes less, i get an error with java heap space out and it wont write any more data like poster, fanart, nfo.
This occurs as well if I scrape for 30-ish titles, write them to disk, then select the next 30. Seems like this java temp space can't handle that many jpgs. I often just close out the jar and open up another instance.
This did not occur in really old iterations of this project. But it has happened since v3.6 or so. I never thought to bring it up but I'd like to see if zuko or wizell can shed some light?
The text was updated successfully, but these errors were encountered: