What?

Calling a function "pushes" that function onto the "call stack", with the idea being that the language pushes a function call onto the stack (think of putting a plate onto a stack of plates), executes the function, and then pops the function off of the stack when it's done, returning control to the function that called it.

When you have a recursive function without a proper break condition (for example: function foo() { foo() }), calling that function keeps putting more and more plates onto your stack and eventually the stack gets too big, falls over, and all your plates break.

Hardware IRQs have nothing to do with it, at least not directly.

Off-topic...

Ow, my mind. Please don't talk about things you don't know anything about.

Though TIE Fighter was a pretty awesome game.

EDIT: Beaten...

TiE fighter is possibly the greatest game of all time...I think PC Gamer rated it #1 a few years ago.
I was actually looking for the CD the other day to try and run it in some kind of DOS sandbox in WinXP, but couldn't find it in the house.

That game was just really, really fun. Here's hoping that LucasArts makes a revamped version somewhere down the pipe.

I literally learned to touch-type because of TIE Fighter's plethora of keyboard shortcuts. I still type badly because of it :(

Best space combat sim ever.

Happened to me a bunch last night too. Did this have anything to do with the background downloader starting up? I noticed when I crashed it was running, I stopped it and I stopped crashing. Maybe just a coincidence though, I can't imagine how the BGD could cause a "stack overflow" error.

Protected operating systems (w2k or newer, any linux) won't let you mess with hardware interrupt handlers. And now I'm actually curious how winXP runs those older games, is it done through interrupt thrown when an unworty process tries to mess with interrupts?

Nothing like that. All you need is a dos emulator, like http://dosbox.sourceforge.net/

Off-topic of course, but the only sensible option for the background downloader IMO is to have it run only after you exit WoW. It's one of the settings choices for it.

Attempting to run a VESA dos program in Windows XP will result in a BSOD.

Can someone post the char byte for the char causing the issue. And is it unicode or ansi? I would assume unicode as WoW is a pretty new game.

Yep, I actually have that checked, or did anyways, but every once in awhile it'll run when WoW is. Maybe some sort of weird thing if I log out of WoW and then go back into it, it'll still run.

I had heard a few other sneaky things that have happened with the background downloader, so thought I'd add my two cents since it seems to be causing crashes. ><

I've had it run twice when I had that box checked. Not sure what the deal was, but I definitely noticed a bit of lag which one would expect.

What exactly is the spam filter, that line was not in my config.wtf at all

This is my first post, so I hope all my little profile bits are set appropriately.

We've had this problem two weeks in a row while clearing BWL. Both times, this happened on Firemaw shortly after we engaged the mob. I think the same subset of the raid disconnected each time the bug got us. We wiped the first time this happened. On the second attempt, the crash happened again--so it's almost as if the problem is related to this particular encounter for us. The same error happened again the next week on the same pull. It very well could be a problem caused by some rogue byte, but having problems occur two weeks in a row in the same exact encounter (not the same server time) is suspicious to me.

I went with a different group this week and had no problem. Not sure if my guild had the overflow problem this week; I'll ask.

EDIT: For general typoishness and de-pronounification.

Someone else mentioned a similar error with a mod somehow outputting the crashing string.
Maybe someone in your raid was using a similar mod that went screwy on something Firemawy?

Its actually an option in the user interface menu while in-game, though the tooltip for the check box isn't very enlightening as to what it does.

Your problem could be from people using outdated bossmods. For instance, on Maexxna people with certain older versions of BigWigs will disconnect as soon as you enter combat. If its the same people every time, I'd check into making sure they've updated all their mods.

I would venture that the only sensible option would be for it to only run when I explicitly tell it to do so. friggen automatic downloaders...

.

For those looking to just get their raid running with this, you can execute these commands in game by throwing a /console before the line.

eg:
/console SET readContest "-1"
/console SET readScanning "-1"
/console SET spamFilter "0"
/console SET profanityFilter "0"

Provided you close WoW properly, it's a one time change (will be written to your config.wtf when you exit).

It defaults to download while playing though, doesn't it? When they introduced it, I don't think it was obvious how to configure it otherwise, if you could back then at all. It's a fairly annoyingly dumb torrent-client, to say the least.


It's answered a bit up in the thread, likely the thing that nixes gold seller sites adresses and the like.

Edit: Bad Abi, thanks Poly.

There's also a bug that disconnects yourself instantly when whispering a particular character code. But I don't think they're related, this sounds more like a bug with the spam filter as the previous posters have said.

The Spam Filter actually prevents you from seeing the same exact chat string from coming up multiple times in quick succession.
Try having a friend make a macro, and then have them spam it to you in party chat. If the spam filter is on you should only see the first one, if it is off you should see all of them. I assume this was added to help alleviate people having their chat frame inundated with some idiots cute spam macro. The problem is that it can also remove messages that you want to see from the game engine if you get identical messages one after another like when a hunter feeds his pet (Spam filter makes it hard to know when to feed again unless you time it some other way).

Tie fighter was the best. Amazing story line, great game play, and decent graphics from what I remember. As far as my (apparent) retarded comment about Stack Overflow, all i remember is that i would get that bug on my new computer a few years ago when trying to play Tie Fighter. I had to hack my way through ancient computer forums to find a solution for such an old game. I finally found something about IRQ, stack overflow, and a quick fix to make it work. It was years ago, please dont jump down my throat for it.