Skip to content
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

Entering nutrition information fills memory #693

Closed
TMP-StephenH opened this issue Feb 5, 2013 · 0 comments · Fixed by #1010
Closed

Entering nutrition information fills memory #693

TMP-StephenH opened this issue Feb 5, 2013 · 0 comments · Fixed by #1010

Comments

@TMP-StephenH
Copy link

Gourmet Recipe Manager 0.15.9 in Fedora 18 x86_64 on an AMD C50 dual-core processor, 4 Gib RAM (Acer Aspire One 722).

Launching Gourmet Recipe Manager adds about 100 MB RAM once the databases finish loading. (< 400 MiB to 461.5 Mib with just the basic program open.

Opening a recipe (in this case, one that is all text with no photograph attached) increases that number to 463.3 MiB.

Switching to the Nutrition tab increases it to 466.4 MiB without doing anything to it.

Switching to the Nutrition tab and attempting to Edit the missing nutritional information balloons the memory use to as high as 3.3 or 3.4 MiB RAM and starts using swap space of almost 400 MiB on top of what it was already using. The program responds very slowly, acting like it is frozen and the CPU usage is pegged to 100% for one of the two processor cores. I can watch the memory use grow while the nutrition editing is opening.

Closing the editing function for nutrition does not seem to free up the additional memory. Even closing the recipe does not halt the growth in memory use. I have watched it brow from 2 to 2.5 GiB over the past minute since closing the recipe before it started to drop and settle at 2.2 GiB.

Only closing the program itself seems to work to free up most of the memory it had taken, but it does not settle back to what it was before I opened the program. It is sitting at 663.1 MiB after closing the program with an additional 203.7 MiB in Swap.

This memory use does not seem like it should be normal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant