R6025 Pure Virtual Function Call!!!

[Aylix]

<p>Any idea on when this is getting resolved? Going on what, two months now?</p><p>I've tried all the 'workarounds', like everyone else, and still crash.</p><p>And to tell you the truth, paying for a game i have to restart 3 times a night (on average) is getting irritating. To put in in a nice sort of way.</p><p>Maybe I don't understand the tech end of this, or how hard it is to fix, but I know that if this happened in any company I have worked for people would have been fired for taking 1/4 as long as this.</p><p>So! What's going on.</p>

[Spyderbite]

<p>Huh? Never experienced this myself and I play many hours per week. Link to where others are having the same problem? Possibly the <a href="http://forums.station.sony.com/eq2/forums/list.m?category_id=45" target="_blank">Technical Support Forums</a>?</p>

[liveja]

<p>I have to agree with Spyderbite .... huh???</p>

[Jrral]

<p><cite>Spyderbite@Venekor wrote:</cite></p><blockquote><p>Huh? Never experienced this myself and I play many hours per week. Link to where others are having the same problem? Possibly the <a href="http://forums.station.sony.com/eq2/forums/list.m?category_id=45" target="_blank">Technical Support Forums</a>?</p></blockquote><p>I've seen it occasionally, usually no more than 3-4 times a month. It's obvious what causes it, but unknown whose piece of code was written by a developer unfamiliar with nasal demons.</p>

[Arslan2000]

<p><cite>Kaethia_Aramae wrote:</cite></p><blockquote><p>Any idea on when this is getting resolved? Going on what, two months now?</p><p>I've tried all the 'workarounds', like everyone else, and still crash.</p><p>And to tell you the truth, paying for a game i have to restart 3 times a night (on average) is getting irritating. To put in in a nice sort of way.</p><p>Maybe I don't understand the tech end of this, or how hard it is to fix, but I know that if this happened in any company I have worked for people would have been fired for taking 1/4 as long as this.</p><p>So! What's going on.</p></blockquote><p>Been seeing this 3 - 4 times a day at times.  I have no clue what causes it either, I just know when it started, right after the launch of TSO. </p>

[Kordran]

<p>Actually, it started right after the "fix" to the crash that people were experiencing on Vista, which started happening on the release of TSO. And interestingly enough, it wasn't a problem with the beta client in TSO; just what they released -- which tells me that they released a version of the client that they didn't expose to public testing.</p><p>The workaround that I use is I disabled multicore support, and added "disable_auto_low_mem_mode 1" to my eq2.ini file. I have to restart the client after zoning a lot (the memory leak that they have had since day 1 is still there), but at least I'm not crashing at inconvenient times.</p>

[Deago]

<p>I will try to make it short and sweet (I am a software engineer so I will try my best.)  Basically its the programmers error and is normally caught at compile time however there are exceptions as many coders know. </p><p>The solution is simple in theory and it is just to debug and find when the pvf call in question is being called and halt the call.  Now when your dealing with a very huge and complex program it can take some extensive concentration. </p><p>I am guessing it is a indirect call otherwise it would have been easy to patch. </p><p>I would like to note on the topic I have many different pc's all running EQ2 and only a select "newer" few have this error.  The older PC's with older graphic/sound cards do not have this issue.  Sooo I would start at looking at parts of the code that revolve around attributes only newer cards can implement.  *shrugs*</p><p>Good luck!</p><p><a href="http://support.microsoft.com/kb/125749">http://support.microsoft.com/kb/125749</a>     puts it very easily with the example.</p>

[Norrsken]

<p><cite>Brazzers@The Bazaar wrote:</cite></p><blockquote><p>I will try to make it short and sweet (I am a software engineer so I will try my best.)  Basically its the programmers error and is normally caught at compile time however there are exceptions as many coders know. </p><p>The solution is simple in theory and it is just to debug and find when the pvf call in question is being called and halt the call.  Now when your dealing with a very huge and complex program it can take some extensive concentration. </p><p>I am guessing it is a indirect call otherwise it would have been easy to patch. </p><p>I would like to note on the topic I have many different pc's all running EQ2 and only a select "newer" few have this error.  The older PC's with older graphic/sound cards do not have this issue.  Sooo I would start at looking at parts of the code that revolve around attributes only newer cards can implement.  *shrugs*</p><p>Good luck!</p><p><a href="http://support.microsoft.com/kb/125749">http://support.microsoft.com/kb/125749</a>     puts it very easily with the example.</p></blockquote><p>could actually be a flaw in a driver and subsystem as well. Or a change to the underlying systems. IE, the drivers have virtual functions that lack implementation in one or another build. Or some subsystem in XP does.</p><p>could be a method (or function) with a long standing "Deprecated" that finally got lost.</p><p>>.< Its really boring digging up bugs in 3rd party software. Eeww.</p>

[Deago]

<p>Anythings possible I am confident that with enough twinkies this dev team might fix the issue <img src="/eq2/images/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" /></p><p>Anybody running xp with this error?  Mine only happends on Vista.  Have not tried it on windows 7 for obvious reasons.</p><p>If it is an issue with a 3rd party then the dev team should find methods to work around the problem. </p>