search

twoolf / circator

Metabolic Compass: A Circadian Monitoring Mobile Health Stack
https://www.metaboliccompass.com
Apache License 2.0
6 stars 1 forks source link

memory footprint large -- can we bring it down? -- #57

Open twoolf opened 8 years ago

twoolf commented 8 years ago

Instruments is suggesting that we're at about 800 MB memory -- at least not crashing the app w/in ten minutes -- note that this went up above 1.3 GB within 15 minutes and that led to slowly responding buttons and then to crash at fifteen minutes

Starts at 25 MB (remains there for about a minute), then to 250 MB, then 385 MB by 1.5 minutes, 480 MB by 2 minutes, 700 MB by 2.5 minutes, 830 MB by 3 minutes (and also timing point for population to be loaded); stable around 830 MB from that point for fairly long; went down to 124 MB after Daily Progress update (took longer than 5 minutes to update; repeated to check, so both times); crash (probably memory) at fifteen minutes in on this round as well

Adding on that both crashes had lldb pointers to HealthManager with either fetchSamples or fetchSamplesOfType being implicated as part of the crash -- dispatch_group_leave also comes up -- so could be related to how we are sending things off for the queue --

conny-the-unicorn commented 8 years ago

Put into backlog to double check and fix