Slick Forums

This is optimized in java. I've profiled this.

Not sure what happens on android. Does it create new instances?

That's what it appears to be doing.

FWIW, here's how I'm testing things:

1) Setup the android app for debug mode via the AndroidManifest.xml file.
2) Deploy to target.
3) Switch to DDMS perspective.
4) Highlight the game process.
5) Select the Allocation Tracker tab.
6) Click Start Tracking button
7) Wait a second or two
Click Get Allocations button

If things were optimized, I'd expect to see only 5 allocations for these objects (one allocation each). Instead, I see a relatively large number of allocations appearing.

If I switch things up and create instances of each Performer() in the constructor and then reference those in the process() method, then I don't see the same allocations occurring in the allocation report.

--tim

Oh wow, I was trusting this wouldn't be an issue since this hasn't been an issue in java since 1.5 I think. Looks like I was wrong. Will fix this soon.

Yes, it is fixed in another fork, but you probably already found it

Anyways, for anyone else interested:

_________________
: bugfixing and performance optimized fork.