Cheat Engine

[kot1990]

I am trying to loop through an arrayList() and then remove some items from it

[Flyte]

I'm not sure how Java handles iterators, but surely every time you attempt to remove something from the list the iterator being used (in the for loop) is being invalidated. Consider adding all of the mobs to be despawned to a separate list, and then afterwards removing them from the original list.

[XSV]

Maybe stick to basics and use a Loop like cometjack suggested, instead of a It.

//Original
for(L2Attackable theMob : mobList)
{
if (theMob.isDead())
{
mobList.remove(theMob);
continue;
}
}


my 2 cents:


//New
for(i=theMob.size();i>0;i--)
{
if (theMob.get(i).isDead())
{
mobList.get(i).remove();
continue;
}
}
sorry if syntax is wrong, haven't used java lately. But you get the idea Xd

[TROLOLOLOLOLOLOLOLOLOLOLO]

Maybe try:

[kot1990]

thank you, I will try all that and then post..

[TROLOLOLOLOLOLOLOLOLOLOLO]

[Slugsnack]

Haven't had time to read the question properly but using iterators or enhanced for loops or even regular forward looping and removing items will fuck it up. You can go backward instead though.

[kot1990]

Solved. Thanks for all help, but now I have another strange issue here. As you know java has Garbage Collection. I created a class that initiates 1.000.000 integers (close to 4MB), then in main created 2 objects of this class (close to 8MB). But the garbage colletion didn't work as I removed any references to these 2 objects.

[Slugsnack]

The garbage collector is not as simple as you think it is. It is not the case that an object having no references to it is immediately garbage collected. Rather, it means that it can be garbage collected by the system at any point from then on. A lot of garbage collectors do not operate immediately once the reference count goes down to 0. In some cases, the extra memory is simply not needed and won't be needed for quite a while so it will just slow the process down to continuously free these regions of memory. In most languages you can force garbage collection or at least hint to the garbage collector that you want it to do some work. In Java, you can do it with System.gc(). However I would advise you not to do this since you'll probably end up slowing it down. Don't worry about the collection. Someone has gone and put a lot of time into designing it so it balances between reclaiming memory and wasting computation. If you fiddle with it, you'll most likely slow it down.

[Flyte]

As an extension for what Slugsnack said, the garbage collector will most likely not bother freeing of that extra 4MB of space anyways. Instead of reallocating more space for new objects, they will use this space and simply write over the old objects as there is an overhead to allocating memory.

[HomerSexual]

I've had some weird experience with the gc where code was malfunctioning if i didn't call the gc. Probably a bad feature on my part (even though anyone i showed the code too didn't have a clue) but calling the gc was good enough.

[kot1990]

thanks for all replies, but how will I be sure that something will be garbage collected? I read somewhere that I have to remove all references and then it will be collected. However in my case I forced the gc with System.gc() and it didn't work the way I did it. I also tried to do it like this.

[Flyte]

[kot1990]