01-29-2024, 10:43 PM
(This post was last modified: 01-29-2024, 10:57 PM by JamesAlexander.)
@BPlus: Yes I did lol. It was all fun and games after a few thousand lines, but about the 10,000 or 20,000 lines, things got serious. I'm glad that I didn't have to edit it after it was made.
@KernelPanic: Yes. It was a matter of running out of memory.
@SMcNeill: "What you have isn't expandable or substainable. You really need to go back to the drawing board and find a better way to automate this process."
--> I think I will have to, because if I hit the limit at 8GB, I'll start disk thrashing from there on out. I see no other choice but to do a virtual swap (because I have a max ram limit of 8GB; I have two 4GB chips on there now, and it is a good system, but it is showing it's age..that is why I have upgraded it with the newer laptop, maxing out at 32GB). With the 8GB system, even with the SSD to mitigate this, the virtual memory on the drive will be thrashing either way. I think I have an alternative way of doing this now that I'm laying this out, though...
@SMcNeill: "Where are you getting the idea that STACK SIZE has *anything* at all to do with this program?? It uses no GOTO, no GOSUB. It has no RETURN statements. There's no RECURSIVE FUNCTION calls. There's *NO USE OF STACK* here at all."
--> For reference: https://communities.actian.com/s/article...Stack-Size or rather, this: https://www.guru99.com/stack-vs-heap.html
@KernelPanic: Yes. It was a matter of running out of memory.
@SMcNeill: "What you have isn't expandable or substainable. You really need to go back to the drawing board and find a better way to automate this process."
--> I think I will have to, because if I hit the limit at 8GB, I'll start disk thrashing from there on out. I see no other choice but to do a virtual swap (because I have a max ram limit of 8GB; I have two 4GB chips on there now, and it is a good system, but it is showing it's age..that is why I have upgraded it with the newer laptop, maxing out at 32GB). With the 8GB system, even with the SSD to mitigate this, the virtual memory on the drive will be thrashing either way. I think I have an alternative way of doing this now that I'm laying this out, though...
@SMcNeill: "Where are you getting the idea that STACK SIZE has *anything* at all to do with this program?? It uses no GOTO, no GOSUB. It has no RETURN statements. There's no RECURSIVE FUNCTION calls. There's *NO USE OF STACK* here at all."
--> For reference: https://communities.actian.com/s/article...Stack-Size or rather, this: https://www.guru99.com/stack-vs-heap.html