Ok, but no need, I got it figured out now, thanks.

Just finished stress testing, frames still dropped, but at exponentially slower rates than before . I think my issue has been solved, I all need is to implement the changes . I will use the Array List, and maybe make an enum of textures, or simply define all the possible textures in the class, not just the default. So many months of development went down the drain after only ~11 days of programming . I'll write in the needed code, stress test, and tell you the results.

1) A normal arraylist gives me a ConcurrentModificationException. I read that I can't catch it, because catching it is only for debugging, and shouldn't be part of the final code.
2) I am saving the textures in the objects' classes..? the only time I am loading textures is in the creation of new objects, or while evolving a star(nebula-star-pulsar-etc..)
3) I don't think jvisualvm works with windows XP 

I'll try stress testing without stars evolving.

jvisualvm?

The game ran, it stopped, no error message, huge lag, no JVM crash log. Eclipse thought the game was still running, had to stop it on eclipse.

stress testing now.

No exceptions, simply java crashing. A quote from the JVM error log

While stress testing, I tested prior to this post, removing entities like meteors, stars, the planet, and removing any one of them still lead to a crash. I suspect it is slick util, as the player's texture will always switch to a weapon texture, just before crashing.

EDIT:
 Added render conservation system, not rendering if texture is outside the screen (still doesn't solve lag),
 Removed much not needed code,
 Separated drawing from updating gameobjects,
New code here:
 http://pastebin.java-gaming.org/530909f4850
Crash is still the same.
 

All too true, removed that exception, as it was no longer needed, added printstacktraces to all exceptions I did need. I will finish up, and upload the new version.

Never let your code carry on running? Isn't that the point of stress testing? If my code didn't need to carry on running, It wouldn't be a game. Problem is there are no Exceptions, but rather Java Virtual Machine crashes. which doesn't pinpoint exactly where the fault was caused. 

XD ok, fine, more work on cleaning.. got it.

1) thanks, no wonder.
2) True, need to clean up after debugging
3) I am notorious for leaving behind tutorials from youtbubers in my code, without cleaning it up afterwards. In result that whole FPS thing is more of a leftover thing.
4) The draw method should be renamed update(), granted.
5) Did you skip this?
6) I do, this is only 1/15 classes I have.

I feel ashamed for having messy coding now :'( (no good for the client anyway.)
I'll re-upload a cleaner version, and simply wait for replies, if my problem isn't already fixed.

Making my sequel to my game, now with 1 player! big issues though.
To be frank, I have no idea what is going on.
I start my game all hunky dory, 160 FPS.
Afterwards, it studders and goes down to a lowly 5-15 FPS.
In those frame hogging moments, some textures are replaced with others.
Then it chrashes. This is my code for the main class.
http://pastebin.java-gaming.org/3b53079405f
 down is my error log from JVM.
http://pastebin.java-gaming.org/b5309804f58

of course not, but why not at least try.

again.. it is a ZERO PLAYER GAME. you really do not do anything.
now if you are wondering how to select your statistics, all you do is press the bottom button to choose a random number to set your health, shield, attack, and then the large button to start the game. However if you experience any bugs, please, please tell me.

This my first official game, after many failures, I have managed to create an addictive ZERO PLAYER GAME.
A Zero player game has pretty much the same aspects as Conway's Game of Life http://en.wikipedia.org/wiki/Conway%27s_Game_of_Life. The Reason I created a zero player game is because I cannot use KeyListeners in an application like mine   . Regardless, it was a milestone for me, and I hope you enjoy.


The basic structure of the game is based on the end score. In the beginning of the game you will be prompted to choose the ships shields, health, and strength. The lower you choose your stats, the higher score you get in the end! Also you get better upgrades. However if you choose stats too low... you will die in the first few rounds...too high and you won't have enough upgrades to survive... You have to try and find a sweet spot that allows you to survive many rounds and get a good score.

When you die, you will see the score screen pop up. You may reply giving a screenshot of your scores, or you may write down everything you got. See if you can get past 200 rounds!

If you'd like, you may download it here: http://www.java-gaming.org/user-generated-content/members/152868/spacegame.jar

UPDATES:
- Moved the download from mediafire to JavaGaming
- May have fixed a bug where images do not display.

To run it, you have to extract the SpaceGame.jar out of the zip file. Then open it with Java, not an Archiver.

Video responses are encouraged!