-
Notifications
You must be signed in to change notification settings - Fork 392
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
Out of memory when IDFEditor reads in a large IDF file #9010
Comments
This is a little tricky to reproduce. If you select the file in EP-Launch and then click on the IDF Editor button it occurs, but does not occur when you open IDF Editor directly and then open the file in it. Another way to reproduce this issue is to at the CMD command line in the IDFEditor folder, type
or what ever is the appropriate path. I was able to reproduce the bug after updating the 9.6 defect file to 22.2 using the 1.51 version of IDF Editor. |
Unfortunately, I have not been able to fix this issue but I do have a workaround: If you are using many Schedule:Compacts input objects in your file, one workaround so that you can open the file in IDF Editor, is to reduce the length of the Schedule:Compact that appears in the Energy+.idd file. Make a copy of the Energy+.idd file called ORIGINAL-Energy+.idd so you can always go back to it if you have to. Then open the Energ+.idd file with a text editor such as Notepad and find the section on Schedule:Compact. After A1000 change the comma to a semi-colon and delete the lines that start with A1001 to A9981, the end of that Schedule:Compact input object description. Save the modified Energy+.idd file and try opening the file in IDF Editor again. This workaround will also be shown in IDF Editor in a dialog box when this out of memory error occurs. |
…number [decent_ci_skip] [actions skip]
IDF Editor added dialog explaining workaround for #9010 out of memory error
Issue overview
There was a "Run-time error '7': out of meomory" warning when using IDFEditor to open a large idf file:
The case file can finish running with EP-Launch tough. This warning is a rare occurrence and the file size may not be the single factor---there seemed to be larger files that can be opened ok without such a warning.
Details
Some additional details for this issue (if relevant):
Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
The text was updated successfully, but these errors were encountered: