About Store Forum Documentation Contact
Donations:
188$/mo



Post Reply 
[RESOLVED] Access violation errors related to File() and Connection()
Author Message
aceio76 Offline
Silver Supporter

Post: #1
[RESOLVED] Access violation errors related to File() and Connection()
Hi Esenthel,

I've been getting this intermittent application crash that I've been trying to troubleshoot, and I could use some insight and advice.

Here are additional call stack messages with "access violation exceptions" enabled through visual studio:
(sample 1)
Worldserver.exe!EE::_Memb::_element() + 0x1c bytes C++
Worldserver.exe!EE::File::put() + 0x9c bytes C++
Worldserver.exe!EE::File::cmpUIntV() + 0x2d bytes C++
Worldserver.exe!EE::Connection::dataFull() + 0x5f bytes C++
Worldserver.exe!WSSendMobPos() + 0xeb bytes C++

(sample 2)
Worldserver.exe!memmove(unsigned char * dst=0x000000e7, unsigned char * src=0x008af57c, unsigned long count=0x00000001) Line 350 Asm
Worldserver.exe!EE::File::put() + 0xa8 bytes C++
Worldserver.exe!EE::File::cmpUIntV() + 0x2d bytes C++
Worldserver.exe!EE::Connection::dataFull() + 0x5f bytes C++
Worldserver.exe!WSSendMobPos() + 0xeb bytes C++

I can typically go back and forth and get either of these messages.


The Output console always has the following:
'Worldserver.exe': Unloaded 'C:\dev\Game\Bin\PhysXDevice.dll'
'Worldserver.exe': Loaded 'C:\dev\Game\Bin\PhysXDevice.dll', Binary was not built with debug information.
'Worldserver.exe': Unloaded 'C:\dev\Game\Bin\PhysXDevice.dll'
'Worldserver.exe': Loaded 'C:\dev\Game\Bin\PhysXCooking.dll'
First-chance exception at 0x0037c06e in Worldserver.exe: 0xC0000005: Access violation writing location 0x000000e7.


Just to make sure I mention it, the attached screenshot is the error I get if I have the exceptions disabled in Visual Studio.


Attached File(s) Image(s)
   
(This post was last modified: 07-20-2012 04:10 AM by aceio76.)
07-19-2012 12:23 AM
Visit this user's website Find all posts by this user Quote this message in a reply
aceio76 Offline
Silver Supporter

Post: #2
RE: Access violation errors related to File() and Connection()
Issue resolved, it was related to multi-threading. Basically, the Connection.send() is executed in a secondary thread, and when I put it back to the main thread, the application started behaving.
07-20-2012 04:09 AM
Visit this user's website Find all posts by this user Quote this message in a reply
Post Reply