You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #14

  Jamash Apr 11, 2012 at 19:57 UTC - 0 likes

  @Semlar: Go

  Thanks for the info, Semlar! I've reported the crash bug on the official forums and am looking for a workaround.

• 

  • Reply
  • #13

  Semlar Apr 04, 2012 at 08:59 UTC - 0 likes

  If what I think is causing this is correct, it has not been fixed in the alpha releases.

  In the file Trainer.lua is

  hooksecurefunc("ClassTrainerFrame_Update", function() LearningAid:GetAvailableTrainerServices() end)
  function LA:GetAvailableTrainerServices()
    for i = 1, GetNumTrainerServices() do
      t.copper, t.isProfession = GetTrainerServiceCost(i)
  

  If ClassTrainerFrame_Update ever fires while you are not talking to a trainer, or if the function is called another way, GetTrainerServiceCost will be called on an invalid index and crash the client. This is because GetNumTrainerServices remains populated after you stop talking with a trainer, so the for loop still iterates over it.

• 

  • Reply
  • #12

  jeffy162 Apr 04, 2012 at 05:48 UTC - 0 likes

  Sorry it has taken so long to respond.

  No, I was not talking to a trainer on any of the occasions that the error occurred. It usually occurred on either a "/rl" or when loading into the world after switching characters.

  I'm crossing my fingers (and everything else I can cross) as I post this, but, the latest revision seems to have solved the problem. I haven't had the error happen since I updated to v1.11.3 (according to the .toc, which also still says Interface 40100), so I'm really hoping that it's gone.

• 

  • Reply
  • #11

  Jamash Mar 20, 2012 at 22:33 UTC - 0 likes

  I see in the crash file 2012-02-02_16.50.17_Crash.txt that the error occurred in the function GetTrainerServiceCost. Were you talking to a class or profession trainer when the game crashed? If so, is that always the case?

• 

  • Reply
  • #10

  jeffy162 Mar 08, 2012 at 17:25 UTC - 0 likes

  Yes, I was using r1045, but have disabled it. It makes no difference, though. I still occasionally get the fatal exception error.

  I have 183 addons installed (but don't use them all at the same time) for 36 characters, yet this addon is always listed as the cause of the error. Something I just don't understand.

  One other thing I don't understand. These lines are in the TOC for the r8 version: " Title: Learning Aid v1.11 Beta 2" and "Version: 1.11 Beta 2". However, there is no mention of the "r8" designation anywhere in the TOC file.

  Last edited Mar 08, 2012 by jeffy162
• 

  • Reply
  • #9

  Hendo72 Feb 25, 2012 at 06:28 UTC - 0 likes

  @jeffy162: Go

  Are you using Ace3 r1045? I'm trying to figure out why you're having an issue and I'm not.

  I have over 100 addons installed and other than a few conflicts, I've never had a fatal exception error (Knock on wood).

• 

  • Reply
  • #8

  jeffy162 Feb 24, 2012 at 06:41 UTC - 0 likes

  Well, I reinstalled using the Curse Client, and had it delete the addon and its' SavedVariables at the same time. Before re-installing I manually checked everything and it was all deleted. Re-installed using the Client. First "/rl" of my UI and got the fatal error again.

  I went over the !BugGrabber report and noticed several Ace3 errors. Now, I keep a stand-alone copy of the alpha version of Ace3 constantly updated in my "AddOns" folder and have never had a problem with it. Until now. All I did was rename that Ace3 folder and the fatal exception has, so far, not happened again. It's been a couple of days since I disabled it, so I'm crossing my fingers (and anything else I can cross) that that is the problem and not Learning Aid or my computer.

  Please allow me to apologize for my ineptitude and causing concern by posting a fatal error bug that I most likely caused.

  Last edited Feb 24, 2012 by jeffy162
• 

  • Reply
  • #7

  jeffy162 Feb 18, 2012 at 22:01 UTC - 0 likes

  Yes, I use the Curse Client. I will uninstall Learning Aid and have the Client delete the SavedVariables also. I'll let you know how it goes.

• 

  • Reply
  • #6

  Hendo72 Feb 18, 2012 at 09:49 UTC - 0 likes

  @jeffy162: Go Have you tried re-installing the addon?

  What do you use to install your addons? If it's Curse Client, uninstall the addon and delete the in-game settings.

• 

  • Reply
  • #5

  jeffy162 Feb 17, 2012 at 01:26 UTC - 0 likes

  Thank you for the link.

  Checked my RAM with MemTest86+ and the Window's memory check and there is nothing wrong with the RAM. Furthermore, there is nothing wrong with my HDD, either, as checked by the Window's "Run-in" test, and Piriforms Defraggler tool.

  I use Spybot Search and Destroy, Ad-Aware and Malwarebytes Anti-Malware for anything not virus related. I use avast! Antivirus for that. None of them have found anything.

  I have no idea why the fatal exception errors happen, but they ONLY happen when this addon is enabled.

  Last edited Feb 17, 2012 by jeffy162