-
Notifications
You must be signed in to change notification settings - Fork 136
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
OOM and RecursionError with large code base #174
Comments
The settings are as follows:
... the project uses .F by default but using a free-form standard (.f90 are partial fortran files to be included in others). |
+1 for this issue. FORD is over 14GB right now and still chugging. Since it's well under my memory on the machine, no big deal. But I want to run FORD for this project on laptops under docker, so I'd like to put it on a memory diet. |
The master branch on here might have fixed these issues. Could you please try running with it? |
I ran current version of FORD on the version of cp2k that existed when this issue was created, using the specified project file options. I was able to collect the graph data withing the recursion error. Generating graphs was still incredibly time-consuming for such a large project, even with the graph size limited. Memory requirements remained large (I suspect some of the slowness was due to using swap-space on the disc) but shouldn't be large enough to crash the program. When I ran with graphs turned off the memory usage did not go above 2GB. It remained quite slow due to the size of your project (over 1000 source files!). At some point it may be worth looking to implement some of the slower parts of FORD using Cython or a similar approach, although that is beyond the scope of this bug report. |
I am trying to run FORD on https://github.com/cp2k/cp2k.
When setting
graph: true
I get (even when restricting to subdir, likesrc/dbcsr
):When disabling graph generation, I get an Out-of-memory first when generating the search index (
search: true
). When disabling the search as well, the process gets killed inGenerating HTML documentation
(even on a machine with 16GB RAM).The text was updated successfully, but these errors were encountered: