How to Recover Project Download Log after App Memory Freeze During Search
Posted: 19 Jun 2025, 19:45
Hi Maksym & Extreme Internet Team,
I am a big fan of the 'After Completion' feature as I like to link a bunch of project searches up together to help automate the daily tasks. Unfortunately, sometimes I get too ambitious and connect too many projects together to where the project runs out of internal memory limits and freezes (becomes non-responsive). Usually when this happens, it is showing over 3 Gb of memory in use and the main thread as 'non-responsive'. Since my system has 32GB of memory and over 20GB is available, thinking it is an internal memory limit issue.
The biggest headache of this scenario is that the last project it is on when it freezes will not lose the images that were downloaded, but the log file for the project becomes corrupt. When I mean corrupt, I mean I am no longer able to 'export the file list' as no data is saved. I understand that the last job did not properly close and this is why it is showing no data when trying to export a project after a failed session.
Question:
- Could it be possible for me to backup all of my project files lists before starting a batch session, so if one of the projects freezes, I can replace the corrupted file list with the previous version... yes, I will lose the last session's data but I will still have all of the previous sessions data which is important to me.. as I tend to only backup the logs ever 100k of files being downloaded... not daily.
- To clarify, is the files I should backup (in case a search is interrupted) is just the '*.dat' files in the 'Data' sub-directory found in the AppData main folder for EPF?
- If so.. then when a search gets corrupted, could I just close or terminate the app (if it is non-responsive)... then reload EPF and try to 'export file list' and if no data is available... to close the app again and copy the corresponding *.dat file that I had backed up.. back into the 'Data' folder, thus copying over the corrupted one... so the next time I run the app... I should be able to 'export file list' for all of the previous files prior to the session that failed. Does this sound like a good work around to avoid losing all of my download log info for a project that ran into a memory issue?
As always, thank you for your guidance... just trying to avoid losing any more download logs for big projects until the memory issue where the download file list can be released (purged) from the memory after the project has completed. ;-)
Best regards,
Phil
I am a big fan of the 'After Completion' feature as I like to link a bunch of project searches up together to help automate the daily tasks. Unfortunately, sometimes I get too ambitious and connect too many projects together to where the project runs out of internal memory limits and freezes (becomes non-responsive). Usually when this happens, it is showing over 3 Gb of memory in use and the main thread as 'non-responsive'. Since my system has 32GB of memory and over 20GB is available, thinking it is an internal memory limit issue.
The biggest headache of this scenario is that the last project it is on when it freezes will not lose the images that were downloaded, but the log file for the project becomes corrupt. When I mean corrupt, I mean I am no longer able to 'export the file list' as no data is saved. I understand that the last job did not properly close and this is why it is showing no data when trying to export a project after a failed session.
Question:
- Could it be possible for me to backup all of my project files lists before starting a batch session, so if one of the projects freezes, I can replace the corrupted file list with the previous version... yes, I will lose the last session's data but I will still have all of the previous sessions data which is important to me.. as I tend to only backup the logs ever 100k of files being downloaded... not daily.
- To clarify, is the files I should backup (in case a search is interrupted) is just the '*.dat' files in the 'Data' sub-directory found in the AppData main folder for EPF?
- If so.. then when a search gets corrupted, could I just close or terminate the app (if it is non-responsive)... then reload EPF and try to 'export file list' and if no data is available... to close the app again and copy the corresponding *.dat file that I had backed up.. back into the 'Data' folder, thus copying over the corrupted one... so the next time I run the app... I should be able to 'export file list' for all of the previous files prior to the session that failed. Does this sound like a good work around to avoid losing all of my download log info for a project that ran into a memory issue?
As always, thank you for your guidance... just trying to avoid losing any more download logs for big projects until the memory issue where the download file list can be released (purged) from the memory after the project has completed. ;-)
Best regards,
Phil