Temporary Memory Crash

I had the program crash several times before in the last few days. It seemed to be caused by the upgrade from 3.26 to the most recent version, though I cannot be sure if that is why it came about. I was upgrading to solve a different issue and the first time I ran it ater the upgrade I had about five minutes before an illegal operation message came up. The message was as follows:

MUSHCLIENT caused a stack fault in module MUSHCLIENT.EXE at 0187:0043841a.
Registers:
EAX=0000003a CS=0187 EIP=0043841a EFLGS=00010202
EBX=00000000 SS=018f ESP=00712000 EBP=00714100
ECX=00000000 DS=018f ESI=01603a8d FS=372f
EDX=00000024 ES=018f EDI=016afdaf GS=0000
Bytes at CS:EIP:
56 3c 3b 8b 44 24 68 6a 00 53 55 50 75 21 83 c7
Stack dump:
016afd8b 01603a8c 00714100 00000000 00000001 00000040 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

This was just the raw data and happened each time I ran the program. I don't know what was causing it, but I redused the buffer sizes of all worlds to 2000 lines and it still cropped up. So I ran DrWatson and got the below output when the error re-appeared:

The application overflowed its temporary memory area.

Module Name: MUSHCLIENT.EXE
Description: MUSHclient
Version: 3.42
Product: MUSHclient
Manufacturer: Gammon Software Solutions

Application Name: Mushclient.exe
Description: MUSHclient
Version: 3.42
Product: MUSHclient
Manufacturer: Gammon Software Solutions

If anyone knows what went wrong, could this be addressed? To note, the Operating system used is Windows 98 SE, and it has been the same for over four years (only one reinstallation required).

EDIT: For some reason, it seems to be related to handling large amounts of text. I examined an object that has about a screen and a half of text to maybe two screens of it and as soon the first quarter of the output showed up, the program crashed again with the same end result of the temporary memory overflow. Now I think I know what caused it, I just need to find out how to fix it so it never does that again when I call up such commands that could give large outputs.

Are you using complex triggers? Maybe trigger matching might consume a lot of memory if given a large piece of data to analyse.

I only have like one trigger per MU*, and they are only active when I want them to be. They are rather simple too. All they do is trigger an automatic +who or plain 'who' (depending on the mu* and it's player listing softcode) every four minutes. I usually leave them disabled unless I will be gone for more than half an hour.

Assuming this is a general bug, can you please paste the text that appears when the object is examined, that causes the crash?

That way, I can try to reproduce it, and see why it is crashing.

Yes, that I can. And I should've said in my last messages that these troggers were actually timers. I forget the difference between the two for a bit. I only had one actual trigger and the trigger was to do an automatic look at a specific object whenever a certain line of text was recieved (like "so-and-so has moved a <chess peice> from <square> to <square>").

Now for the text I got when it crashed...


ex *Mark
Mark(#366PUenACF)
Type: Player Flags: UNFINDABLE ENTER_OK NO_COMMAND ANSI COLOR FIXED
%r%tStanding at an even five foot, ten inches, this fox looks like your average Conerian Military officer, fancy pins and all. His face is almost all tan fur, running around both saphire [ansi(hb,blue)] eyes and down under his chin leaving the top of his muzzle and up between the eyes and the rest of his face the standard [ansi(hr,red)]. His ears have a [ansi(h,whiteish)] inner tip that extend about two inches from the very tip down into his ears.%r%tHe wears a scarlet [ansi(hr,red)] military uniform jacket that's a cross of british and early nepolean, with [ansi(y,gold)] shoulder pads and sports pins along with rank insignia the equivilant of a wing commander. Under the open jacket is a

That's about as far as it will display in the output window before the program overflows it's temporary memory. This seems to be something that happens whenever any kind of large text display is sent since I took time to reproduce it through one MUSH only and by just examining this particular player. The normal output is about six screens long (using 800x600 resolution).

NOTE: As of this writing, I uninstalled the program, rebooted and did a clean reinstall backing up only my world files and logs before starting the entire re-installation proccess. The isue doesn't seem to be a problem anymore but I am keeping my fingers crossed that it's only a specific bug that only happens if something messes up the way the program operates (like improper shutdown or virus).