Memory Leak in Transition internal code?

Solar2D Advanced Graphics
#1

Hi,

Has anyone, using transitions massively, noticed any memory leak after moving to 2.0?

I’ve ported one of my games and on the first page - the main menu, I have a lot of small snowflakes going down.

on V1, when moving from the main menu to another page and back, memory size returns to its initial value.

however, on V2 I see gradual increase when moving out and back to the main page.

No code has been changed regarding transitions in the app. only the mandatory changes due to 2.0.

would appreciate any input. I’m hesitant to release the new version to the app store in this state and I do not want to go back to V1.

#2

What versions of Corona SDK are you comparing?

When you say V1 and V2, it’s a bit confusing because we released a new Transition 2.0 library in our Graphics 1.0 daily builds and there have been additional fixes to T2.0 in the G2.0 daily builds (though everything should be in 2100).

Thanks

Rob

#3

I’m comparing specifically build 2114 with build 1260.

when mentioning V1 and V2 I refer exclusively to Graphics V1.0 or Graphics V2.0.

I’m not familiar with the new transitions library, unless its replacing the previous library with no effort from my side.

the transitions I refer to are all using the same api:  local t = transition.to(obj, {time=300, duration=500, x=x1, y=y1, etc})

I hope this helps locate the issue. I have two projects already transferred and waiting apple approval.

#4

The new Transition library was put into place  sometime between 1212 and 1260.  There were other transition bug fixes between 1260 (the last G1.0 build) and the current 2100 public G2.0 build.   There could be other things that might be leaking memory.   We will need to have a project that shows the bug, but it needs to be the minimal project to demo the bug and then file a bug report using the link at the top of the page.

It needs to include your config.lua and build.settings as well as your code and resources.

Rob

#5

Well, its not the new lib since I’m using 1260 as the control build and it doesn’t leak there. so there must be something after. 

I will try to compile a simple test for you and open a PR.

#6

Can you submit a bug report with a sample that’s leaking?  The engineers are wanting to track this down and they need some data points.  Make sure it’s a complete project with config.lua and build.settings files.

Thanks

Rob

#7

What versions of Corona SDK are you comparing?

When you say V1 and V2, it’s a bit confusing because we released a new Transition 2.0 library in our Graphics 1.0 daily builds and there have been additional fixes to T2.0 in the G2.0 daily builds (though everything should be in 2100).

Thanks

Rob

#8

I’m comparing specifically build 2114 with build 1260.

when mentioning V1 and V2 I refer exclusively to Graphics V1.0 or Graphics V2.0.

I’m not familiar with the new transitions library, unless its replacing the previous library with no effort from my side.

the transitions I refer to are all using the same api:  local t = transition.to(obj, {time=300, duration=500, x=x1, y=y1, etc})

I hope this helps locate the issue. I have two projects already transferred and waiting apple approval.

#9

The new Transition library was put into place  sometime between 1212 and 1260.  There were other transition bug fixes between 1260 (the last G1.0 build) and the current 2100 public G2.0 build.   There could be other things that might be leaking memory.   We will need to have a project that shows the bug, but it needs to be the minimal project to demo the bug and then file a bug report using the link at the top of the page.

It needs to include your config.lua and build.settings as well as your code and resources.

Rob

#10

Well, its not the new lib since I’m using 1260 as the control build and it doesn’t leak there. so there must be something after. 

I will try to compile a simple test for you and open a PR.

#11

Can you submit a bug report with a sample that’s leaking?  The engineers are wanting to track this down and they need some data points.  Make sure it’s a complete project with config.lua and build.settings files.

Thanks

Rob