03-23-2013, 05:08 AM
Yeah, I tried the following scenario:
-Water simulator off
-Lava simulator on
-Switched m_LavaSimulator and the m_pDefaultWorld to Public membes
-Applied a try catch block on the new operator in the cChunkMap::cChunkLayer::GetChunk() function to prevent an unhandled exception, and see what happened.
-Put a breakpoint in the catch block to see what's going on at the time of the exception
Result:
-The bad alloc exception happened
- For Lava:
m_TickDelay: 30
m_AddSlotNum: 22
m_SimSlotNum: 23
m_TotalBlocks: 2473
-Created a crash dump that is 2gb in size (can't break that into 1mb slices and upload it to the forum hehe
)
I can try to see where is the most memory used to see if it help us track down the issue.
-Water simulator off
-Lava simulator on
-Switched m_LavaSimulator and the m_pDefaultWorld to Public membes
-Applied a try catch block on the new operator in the cChunkMap::cChunkLayer::GetChunk() function to prevent an unhandled exception, and see what happened.
-Put a breakpoint in the catch block to see what's going on at the time of the exception
Result:
-The bad alloc exception happened
- For Lava:
m_TickDelay: 30
m_AddSlotNum: 22
m_SimSlotNum: 23
m_TotalBlocks: 2473
-Created a crash dump that is 2gb in size (can't break that into 1mb slices and upload it to the forum hehe
)I can try to see where is the most memory used to see if it help us track down the issue.