If you are using Win98 or something earlier you can change the space allocated for stack memory by editing your config.sys (or config.dos in some setups) file. This is a simple change, but will not help except for programs running on your own machine. Similar "adjustments" may apply to some MAC versions.

Troubleshooting Stack Overflow Errors: Note that this article (KB 145799) applies only to Win98 and earlier versions of Windows, and only to programs running locally on your own machine.

Later Windows versions use dynamic memory management that should pretty much eliminate the problem without your attention.

Since you only get the error at a specific site, it's likely that you're seeing an error on the site server, and changing your machine won't help. Most stack overflows are considered "program errors," and merit a complaint to the site; but there's little you can do on your own machine that will help, since the program at fault isn't (shouldn't be) running on your machine.

On some server systems, stack overflow can be "exploited" in a way similar to the "buffer overflow" holes in numerous user programs, to load malicious software on the server; but there are no reported "exploits" applicable to user machines (at least not in the past 20 years). The sudden appearance of this message could mean that someone has tried to "take over" the page server, probably for purposes of sending spam or for a DDNS attack somewhere. It does not necessarily mean the attempt was successful, if the page admins were just not thorough about completely cleaning up the worm that made the attack. Decent AV software would block any virus "payload," but might not stop the "agent" that produces the stack overflow.

If an attack on the server was successful, it means that the page/site management has failed to apply security fixes that have been available for at least several years - a good enough reason to bring it to the attention of their sysadmin; although what you're seeing is most likely just a poorly constructed page script.

The advice to ignore is probably appropriate in your case, although I would suggest complaining (politely?) to the affected site.

John