Stack Overflow issue?

[FanFromArizona]

Is everyone getting a stack overflow on line 95 issue?

[The_Sonny_Of_Sammy]

Is everyone getting a stack overflow on line 95 issue?
It started happening to me yesterday. What does it mean? I'm not real computer savvy, so if this is a serious problem any help will be welcome also.

[redskin_rich]

No idea on what you all are talking about. How about a little description?

[AliBabba]

Is everyone getting a stack overflow on line 95 issue?

i haven't seen it

[BurgundyNGold]

I got it once yesterday. My DSL at home has been crap for about a week. Finally, on Saturday night it just went out. When I came back from work last night, I could see the Verizon site telling me to install my DSL. Once I did and came to hR I saw that prompt once. But not anymore.

[NCskinsfanatic]

I was getting it yesterday but not today, my dsl has its ups and downs also...

[BurgundyNGold]

What's interesting is that "stack overflow" errors happen when the amount of memory allocated is used up and the program tries to use more. I have seen this happen primarily in infinite loop or infinite recusion situations. For example, if function A calls into itself without a break or if function A calls function B, B then calls A and so on. There might have been some problems in the JavaScript on the front page ad software or something.

[skinfan43]

What's interesting is that "stack overflow" errors happen when the amount of memory allocated is used up and the program tries to use more. I have seen this happen primarily in infinite loop or infinite recusion situations. For example, if function A calls into itself without a break or if function A calls function B, B then calls A and so on. There might have been some problems in the JavaScript on the front page ad software or something.
You sound pretty smart there, Curtis.
I got the stack overflow before...nasty stuff, needed a power plunger to fix it.
(My intelligence factor rivals yours, as you can plainly tell.)

[FanFromArizona]

I received the problem both on work computer and on 2 home computers.

I have periodically experienced it quite a few times the past 3 days.

[hail2skins]

Actually, it was us playing around to see who actually visits the content side of the site. Seriously though, chances are you experienced it most of yesterday and part of this morning. It should be done now. When you experienced it, you probably didn't notice that the menu at the top was missing. We fixed it this morning. Sorry for the inconvience.

[hail2skins]

Also, hit refresh on your browser just in case the site is cached on your computer.

[BurgundyNGold]

You sound pretty smart there, Curtis.
I got the stack overflow before...nasty stuff, needed a power plunger to fix it.
(My intelligence factor rivals yours, as you can plainly tell.)
LMAO! I should not have rule out THAT kind of stack overflow as the culprit, lol.

[Keino]

What's interesting is that "stack overflow" errors happen when the amount of memory allocated is used up and the program tries to use more. I have seen this happen primarily in infinite loop or infinite recusion situations. For example, if function A calls into itself without a break or if function A calls function B, B then calls A and so on. There might have been some problems in the JavaScript on the front page ad software or something.


Im sorry, but thats not very interesting at all actually.

[BurgundyNGold]

Im sorry, but thats not very interesting at all actually.
Such is the terrible price you pay for stumbling into a thread with "stack overflow" in the title, lol.

[Keino]

Such is the terrible price you pay for stumbling into a thread with "stack overflow" in the title, lol.


LMAO - I got the message so I wanted to see why I was getting it. I had no idea it would turn into a "Principles of Stack Overflow 101" Course.

[HAWGZHEAD]

For example, if function A calls into itself without a break or if function A calls function B, B then calls A and so on. That made me go cross eyed for about 5 minutes. I feel like I just took the SAT again.

[FanFromArizona]

What's interesting is that "stack overflow" errors happen when the amount of memory allocated is used up and the program tries to use more. I have seen this happen primarily in infinite loop or infinite recusion situations. For example, if function A calls into itself without a break or if function A calls function B, B then calls A and so on. There might have been some problems in the JavaScript on the front page ad software or something.

I understand that perfectly clear, going from one computer guy to another. :rolleyes:

[SpicyMcHaggis]

I understand that perfectly clear, going from one computer guy to another. :rolleyes:
..and to another..unfortunately I know what he is talking about too..we could form our little Nerd group...

[BurgundyNGold]

I understand that perfectly clear, going from one computer guy to another. :rolleyes:
I guess that was a terrible example. I just re-read it and I can see how it might seem confusing. Honestly, I can't think of a way of putting it aside from talking about an infinite loop. This is a simplistic example, but it might help to explain how a stack overflow can occur:

Imagine you have a process for cutting the grass that has 10 steps. So, you go outside and start the process, performing the 10 steps required to cuts the grass. However, step 10 tells you to go and cut the grass again. Every time you finished cutting the grass and reached step 10, you'd just start cutting the grass again. This is an example of an infinite (recursive) loop because without some logic to tell you to stop cutting the grass, you'll just keep doing it. It is very common that this happens in code that does not account for all possible outcomes. You get a lot of that in JavaScript.

[SpicyMcHaggis]

I guess that was a terrible example. I just re-read it and I can see how it might seem confusing. Honestly, I can't think of a way of putting it aside from talking about an infinite loop. This is a simplistic example, but it might help to explain how a stack overflow can occur:

Imagine you have a process for cutting the grass that has 10 steps. So, you go outside and start the process, performing the 10 steps required to cuts the grass. However, step 10 tells you to go and cut the grass again. Every time you finished cutting the grass and reached step 10, you'd just start cutting the grass again. This is an example of an infinite (recursive) loop because without some logic to tell you to stop cutting the grass, you'll just keep doing it. It is very common that this happens in code that does not account for all possible outcomes. You get a lot of that in JavaScript.
Or, to keep to your example, let's say you ( the process or application) have a yard (which is your memory stack)..well, you start cutting the grass (occupying blocks of memory in your stack), and when you are finished (the stack is full), you don't stop, but start cutting your neighbour's grass(the memory stack of another process or the memory allocated for your code)..well, he's gonna be pissed (stack overflow error). Unless of course he asked you to cut his grass, but that really has nothing ot do with the example.

[BurgundyNGold]

Or a more apropos example:

The Redskins want a player. But they haven't got any draft picks as ammunition. So they trade away all of their draft picks for the next year to acquire said player. Since the Redskins have no depth or have made the wrong choices, they have a poor record and holes to fill the next season. Then the next year comes around, so they do the same thing all over again. Clearly, this would be poorly written code, so I ask you, shouldn't this be considered a poorly written process?

:D

[SpicyMcHaggis]

Or a more apropos example:

The Redskins want a player. But they haven't got any draft picks as ammunition. So they trade away all of their draft picks for the next year to acquire said player. Since the Redskins have no depth or have made the wrong choices, they have a poor record and holes to fill the next season. Then the next year comes around, so they do the same thing all over again. Clearly, this would be poorly written code, so I ask you, shouldn't this be considered a poorly written process?

:D
Well, it could be that a poorly written process miraculously works for a while (end of 2005 season), but sooner or later, the bugs will start showing (2006 season), so the programmer must be fired (Vinny).

[BurgundyNGold]

Or, to keep to your example, let's say you ( the process or application) have a yard (which is your memory stack)..well, you start cutting the grass (occupying blocks of memory in your stack), and when you are finished (the stack is full), you don't stop, but start cutting your neighbour's grass(the memory stack of another process or the memory allocated for your code)..well, he's gonna be pissed (stack overflow error). Unless of course he asked you to cut his grass, but that really has nothing ot do with the example.
Not bad, lol. I think your example works best for ilustrating allocated vs. unallocated memory and for not effectively deallocating memory because technically, it doesn't matter where we are cutting the grass after we're done the first time if we didn't deallocate after the first pass.

Next week, we discuss pointers, lol.

[BurgundyNGold]

Well, it could be that a poorly written process miraculously works for a while (end of 2005 season), but sooner or later, the bugs will start showing (2006 season), so the programmer must be fired (Vinny).
This is what could be referred to as a bug, lol.

[SpicyMcHaggis]

Not bad, lol. I think your example works best for ilustrating allocated vs. unallocated memory and for not effectively deallocating memory because technically, it doesn't matter where we are cutting the grass after we're done the first time if we didn't deallocate after the first pass.

Next week, we discuss pointers, lol.
Pointers, and pointers vs. arrays...1st lesson, why is p[0] equal to *p?
Lol...

[SpicyMcHaggis]

This is what could be referred to as a bug, lol.
Of the nastiest kind..the one that makes you think that everything is going well, but then, when you go and make your presentation (our 2006 season in which we were supposed to make a SB run), everything crashes (5-11) and you get fired (the missing link).

[BurgundyNGold]

Of the nastiest kind..the one that makes you think that everything is going well, but then, when you go and make your presentation (our 2006 season in which we were supposed to make a SB run), everything crashes (5-11) and you get fired (the missing link).
http://www.youtube.com/watch?v=9rXWr6Ezax4

;)

[SpicyMcHaggis]

http://www.youtube.com/watch?v=9rXWr6Ezax4

;)
That video was exactly what I had in mind when I posted...lol...

[FanFromArizona]

I guess that was a terrible example. I just re-read it and I can see how it might seem confusing. Honestly, I can't think of a way of putting it aside from talking about an infinite loop. This is a simplistic example, but it might help to explain how a stack overflow can occur:



The best example that I can give is along these lines:

x = 1 DIVIDED BY 3

Solve for x. (think: Global Thermonuclear War or Tic-Tac-Toe from Wargames: it will keep going and it won't figure out when to stop)

--or-

x=0
FOR x = 1 to 5
SAY HI
x= x - 1
END

[FanFromArizona]

Or a more apropos example:

The Redskins want a player. But they haven't got any draft picks as ammunition. So they trade away all of their draft picks for the next year to acquire said player. Since the Redskins have no depth or have made the wrong choices, they have a poor record and holes to fill the next season. Then the next year comes around, so they do the same thing all over again. Clearly, this would be poorly written code, so I ask you, shouldn't this be considered a poorly written process?

:D

Stack overflow does not apply to the Redskins. It's called DRAFT ABUSE! :rolleyes:

[BurgundyNGold]

The best example that I can give is along these lines:

x = 1 DIVIDED BY 3

Solve for x. (think: Global Thermonuclear War or Tic-Tac-Toe from Wargames: it will keep going and it won't figure out when to stop)

--or-

x=0
FOR x = 1 to 5
SAY HI
x= x - 1
END
Yeah, that's going to be easier for folks. ;)

[redskinz#1fan]

Im sorry, but thats not very interesting at all actually.

I'm with you on this one Sean!!

[housefull]

i haven't seen it
I got it once yesterday. My DSL at home has been crap for about a week. Finally, on Saturday night it just went out. When I came back from work last night, I could see the Verizon site telling me to install my DSL. Once I did and came to hR I saw that prompt once. But not anymore.
__________________

[CarMike]

I got it once yesterday. My DSL at home has been crap for about a week. Finally, on Saturday night it just went out. When I came back from work last night, I could see the Verizon site telling me to install my DSL. Once I did and came to hR I saw that prompt once. But not anymore.
__________________

Who pulls up a thread that is almost 3 years old? Mike, is this a bot?

[CNYSkinFan]

Who pulls up a thread that is almost 3 years old? Mike, is this a bot?
it has to be, he is quoting a post by b&g

[hail2skins]

Who pulls up a thread that is almost 3 years old? Mike, is this a bot?I doubt it.

[BurgundyNGold]

it has to be, he is quoting a post by b&g
That doesn't mean the poster is a bot. It just means the poster makes poor choices about what to read lol.

[Keino]

That doesn't mean the poster is a bot. It just means the poster makes poor choices about what to read lol.

And 3 years later, it sill isn't very interesting....

[BurgundyNGold]

And 3 years later, it sill isn't very interesting....
May your stacks never overflow. Otherwise, you're going to be in a world of nerd hurt lol.

[Keino]

May your stacks never overflow. Otherwise, you're going to be in a world of nerd hurt lol.

My stack overflow issues are of a different sort. My stack ain't overflowin' and it's an issue dammit.