Log in

View Full Version : A pure virtual function was called. The application will now terminate.


Arcturys
01-11-2012, 01:08 AM
<p><strong>"A pure virtual function was called. The application will now terminate."</strong></p><p>That is the message I am mysteriously receiving today. I have never seen that in the entire time I've been playing the game. This is brand new.</p><p>I was heading by flying mount to the pad in The Sundered Frontier where you access the Library, Research Halls and Palace, as I've been doing nearly every evening for weeks now. When I was nearly there, the game lagged out hard and then froze up. I tried CTRL + ALT + DEL to bring up the Task Manager, but it had locked up my entire system. It took nearly two minutes for me to finally get the Task Manager to pop up, but then it refused to let me close EQ2. I kept telling it to shut down the program, but EQ2 would stay in the Task Manager's processes tab. After a couple more minutes it finally shut it down.</p><p>I rebooted then logged back into game. When I was in The Sundered Frontier, I continued on to the launch pad and selected the Erudin Library teleporter. The game just sat there for about a minute or so, but everything was frozen. It was like it was about to take me to the loading splash screen, but then stalled. Finally it went to the splash screen, but then it froze on "creating zone."</p><p>After another minute or so, EQ2 kicked me out and I got a small nondescript error message box that said, as indicated above: "A pure virtual function was called. The application will now terminate." Five seconds later a second message box popped up with the exact same message. Another five seconds passed and then a third identical message box appeared. That was the extent of it. I clicked on close for the first box, but then the other two boxes hung up and wouldn't let me click them. After another minute or so, I finally got the Windows error message box stating that EQ2 had encountered an error and needed to close. I clicked okay, and then I came here. I haven't tried logging back in a third time.</p>