same problem man. just logged on and it all was gone
would be great if there was a way to retrieve the data.

Posted by: Lerner of Daggerspine on Apr 26 2006, 01:28 PM
Hello-

I'm having the same issue as described above, here is the info requested at the top of the page...
Addon version: 3.4.0.0817 (Platypus)
WoW client version and language 1.10.1 (5230) - English
Interface version 11000
Short classification of the problem Basic Usage
Full description of the issue: Loss of previous scan data. When logging in this AM, I received a LUA error which I have been unable to duplicate and stupidly did not write down, and after clicking ok, and going to the AH, all of my previous scan data was missing. I researched this on this site and found that the scan data is stored (I think) in the Auctioneer.lua file. My auctioneer.lua.bak file is several months old, so that didn't help. I did a new scan and tha data seems to be holding, but I'm wondering what happened to my old data. Thanks in advance for any help you can provide.

Hi, everybody. I honestly don't know whether my problem is the same as that of the rest of the people in this thread, but I've been having the same symptom so I'm posting as part of the thread rather than starting a new one.

Addon version: 3.4.0.0817 (Platypus)
WoW client: 1.10.1 (5230) English language version
Interface version: 11000
Short classification of the problem: LUA error (possibly Basic usage)

Full description:
I will log into the game, and receive a "constant table overflow" error when loading Auctioneer. At this point when I log out of the game my Auctioneer.lua file is basically reset and becomes a nice trim errorless 2kb file.

What's particularly tricky for me is that I haven't been able to replicate it very often, at least not often enough for me to isolate what is wrong, but I first started noticing it happening to me sometime around last week. I had to use my backup .lua file, reverting to data that was about a month old. Ever since then I've been trying to pay attention and I have noticed that prior to the error occurring I will often have completed an auction scan. Typically at some point in the scan my character will have gone afk. The AH will usually have about 200 auctions so a full scan will almost invariably result in the game forcing an afk state on me. I will come back and notice that my auctions have completed scanning, and I will log out of the game.

After this I will log in and get the "constant table overflow" in the nice red Letters of Fear. If I preserve the .lua file in order to preserve the data and then replace it after logging out, I still get the error message.

So, as best as I can tell, I am losing my .lua data after completing a full auction scan. It doesn't happen every single time I scan an auction, but it has happened about 3-4 times in the last two weeks, as best as I can recall. Now that I've started paying attention to it, the only thing that I have noticed with consistency is that I'll leave a character scanning, it'll take a long time to scan the 200 or so auctions, the char will go afk, I will wait for the confirmation of the end of the scan, I move around my char to turn off afk, and then I log out. After that logging in will result in the dreaded error message. I do not see how going afk could be related to this since that seems like an apples and oranges issue, but I am mentioning it anyway since it has definitely happened each time I've been watching for the error to creep up.

My .lua file is currently about 24 mb large, and I have tried setting my addon memory usage to 256 mb from 128 mb, but it doesn't prevent the error from occurring so I know that it's not an issue of the file becoming too large (also evidenced by the fact that the game interface doesn't slap me in the face demanding more memory) but I figured I'd try that just to see.

I'm sorry for the redundancy in the post, I'm trying my best to be specific to help you guys out and I have no experience being a bug tracker. Let me know if you need any more data, or if what I'm saying seems to help you pinpoint something specific. I've taken to backing up my data a lot more often, almost to the point of making a copy of my .lua file prior to each scan, out of paranoia. I think this last error only sets me back about 2 days, which at the most is 2 scans for me, but I would still like to live a more carefree life.