Legend leak in version 3.0.1

[laizf]

When use instruments to analyze memory leak, found Legend is leaked, but cannot find the reason. The stack trace is shown in the image above.

[laizf]

It's seems the same bug with issue:#2416 "Memory Leak in BarChartView Data".

[laizf]

My XCode Version is 8.3 (8E162). I ever used old version XCode to check memory leak about two month ago, and no leak found that time. I think you should update your XCode to the latest version if you want to reproduce this bug.

[thierryH91200]

this is the latest version sorry

[laizf]

And can you reproduce or solve this problem? @thierryH91200

[laizf]

@liuxuan30

[liuxuan30]

Update:
See my comments below, when pop back, the same leaked object is freed

OK, legend seems do have a leak, but I can't reproduce #2416, so let's make it separate.

[laizf]

The ref count is -1 finally, but instruments still mark it as leak. The instruments file is too large to upload, so I just show you the screenshot:

[liuxuan30]

No, I tried when you pop back, the leaked object is freed then:

When your chart is displaying, I can't say it's our problem, as when the chart get destroyed, the objects saying leak is also freed.

You can try on your side, just pop back or make your chart dealloc

Last year at WWDC 2016, apple's people also confirm some of the false leak is their bug (radar 26817765), just like this. So please double check.

I have filed a radar 32189235 to Apple

[laizf]

Copy

[liuxuan30]

If you sure it's freed, I will close the related issues.

[laizf]

I think so!