A crash I just can't understand

[SeaNymph]

After posting this crash report on the Simply Horses thread they couldn't help me and well the crash doesn't seem to have anything to do with that mod at all.  So heres the report I looked around and didn't manage to find anything that was like this one. I installed forge first on a clean minecraft .jar after that i put the mod in the mods folder and everything was running fine. I later added optifine which many of the other people active on that mod forum are using without this error. The creator of the mod looked at the error and wasn't sure what was going on either. I did search for another error of this kind on your forums but none looked like this that i found. Just one last thing This crash occurred while I was walking around It happened before and after i got a fresh jar and reinstalled everything it was fine including optifine.

 

 

--- BEGIN ERROR REPORT a2c65d12 --------

Generated 11/7/12 12:55 AM

 

- Minecraft Version: 1.4.2

- Operating System: Windows 7 (amd64) version 6.1

- Java Version: 1.6.0_31, Sun Microsystems Inc.

- Java VM Version: Java HotSpot 64-Bit Server VM (mixed mode), Sun Microsystems Inc.

- Memory: 240209664 bytes (229 MB) / 526843904 bytes (502 MB) up to 954466304 bytes (910 MB)

- JVM Flags: 2 total; -Xms512m -Xmx1024m

- AABB Pool Size: 2478 (138768 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used

- FML: MCP v7.19 FML v4.2.6.422 Minecraft Forge 6.0.1.341 Optifine OptiFine_1.4.2_HD_B2 4 mods loaded, 4 mods active

mcp [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available->Available->Available

FML [Forge Mod Loader] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available->Available->Available

Forge [Minecraft Forge] (coremods) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available->Available->Available

SimplyHorses [simply Horses] (SimplyHorses_1.4.2_pre5.1A.zip) Unloaded->Constructed->Pre-initialized->Initialized->Post-initialized->Available->Available->Available

- Is Modded: Definitely; 'forge,fml'

- Profiler Position: N/A (disabled)

- Vec3 Pool Size: 568 (31808 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used

- Player Count: 1 / 8; [ih['Perngirl'/167, l='New World', x=6.49, y=69.00, z=832.16]]

- World New World Entities: 0 total; []

- World New World Players: 0 total; []

- World New World Chunk Stats: ServerChunkCache: 0 Drop: 0

- Type: Integrated Server

 

java.util.ConcurrentModificationException

at java.util.AbstractList$Itr.checkForComodification(Unknown Source)

at java.util.AbstractList$Itr.next(Unknown Source)

at ib.b(PlayerManager.java:71)

at ie.b(WorldServer.java:136)

at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:648)

at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:585)

at bcb.q(IntegratedServer.java:110)

at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:492)

at fp.run(SourceFile:818)

--- END ERROR REPORT fa541dbf ----------

 

 

 

[keepcalm]

java.util.ConcurrentModificationException

Read the EAQ

[SeaNymph]

I did and while I understand it doesn't state that it deals with forge it doesn't claim the crash comes from any of the installed mods I have which is few. I came here hopping someone could at least explain what the crash means so I can try to track down the cause.

[SanAndreaP]

I remember that kind of crash, because I encountered it many times while updating Clay Soldiers to 1.3.2. I can definetly say that is a mod issue! The problem is that the mod tries to do things with the server thread and manipulate something in the client thread while doing so (or vice versa).

The problem in Clay Soldiers was that I spawned particles with the server thread and old, SP code from 1.2.5.

 

So yes, it's NOT a forge issue! It's a mod issue.

[SeaNymph]

Well I'll go back and talk to Avii about it but so far no one else using the mod is having the crash