kaiserfarrell / core-plot

Automatically exported from code.google.com/p/core-plot
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Memory leaks (application crash) on loading 15 graphs at a time #443

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Don't know if this is the right place to put my concern, but just thought to 
raise it so that i can get some help from the core-plot community.

I have an application which plots 15 graphs off data which is pulled from the 
server through web services.

The problem is that if i sync and recreate the graphs for more than 2 times, 
the application crashes with memory issue. The error which is returned is 
"CoreAnimation: failed to allocate xxxx bytes"

We have updated to the latest release of core-plot but that still gives the 
problem. We are using ARC as well.

Any help would be really appreciated.

Original issue reported on code.google.com by jai.uni...@gmail.com on 10 Jul 2012 at 9:11

GoogleCodeExporter commented 8 years ago
Also, the data set on which graphs are created has 12,000 rows with 50 columns. 
This data is saved in local SQLite storage.

Original comment by jai.uni...@gmail.com on 10 Jul 2012 at 9:13

GoogleCodeExporter commented 8 years ago
That is quite a lot of data to pull into memory on an iOS device. You could do 
some profiling with instruments allocations tool to see what sort of memory 
usage you have.

If it turns out to just be too much data, stored in too many graphs, you either 
have to reduce the amount of data by culling some points, or you have to reduce 
the number of graphs (eg show a few at a time). 

There are physical limitations on iOS devices, and there is not much Core Plot 
can do to help. It has to have the data to draw.

Original comment by drewmcco...@mac.com on 10 Jul 2012 at 9:16

GoogleCodeExporter commented 8 years ago
We do agree, but Roambi does the same thing. If it can show around 50 reports/ 
graphs... we should be able to do it.

Also, we are not facing any problem with the data storage but the problem is 
with the Graphic Engine.

Please suggest

Original comment by jai.uni...@gmail.com on 10 Jul 2012 at 9:37