At some point, usually during the editing of a package, the CPU usages spikes up to 100% while the memory consumption goes up 10X. I have two instances running, one using 48,640K and one using 443,844K with no editors open and no current connection. Once the memory jumps up, it never goes back down.
Can you say "memory leak"?
(Version 7.1.0.1337)
After restarting, I opened the same package file and continued where I left off. The package has 6909 lines with this structure:
1: CREATE...
2-266: commented with /* */
267-783: mostly code
785-6908: commented with /* */
6909: END;
As soon as I typed /* at line 500 to comment out some more code, the CPU and memory shot up. Is it trying to be smart with the gutter highlighting? And why doesn't closing the Program Window release the memory?
Can you say "memory leak"?
(Version 7.1.0.1337)
After restarting, I opened the same package file and continued where I left off. The package has 6909 lines with this structure:
1: CREATE...
2-266: commented with /* */
267-783: mostly code
785-6908: commented with /* */
6909: END;
As soon as I typed /* at line 500 to comment out some more code, the CPU and memory shot up. Is it trying to be smart with the gutter highlighting? And why doesn't closing the Program Window release the memory?