Forums mIRC Help mirc problem...

Once I enter a server and then a channel, as soon as I try to type in the box at the bottom, this error pops up:
-
Debug Assertion Failed!
Program: C:\PROGRAM FILES\MIRC\MIRC.exe
File: dbgdel.cpp
Line: 47
Expression: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)
-
Is there anything I can do to overcome this? Reply Soon!

this is a new one for me. I googled dbgdel.cpp and mostly ended up with my eyes crossed since its C++ stuffs so i could be way off base with my speculation/guess. As near as i can figure, it may have to do with an incorrect memory allocation problem and/or corrupt dll. Have you downloaded any dlls of late to use with mIRC? New scripts?

Are you joining the network server with mIRC or thru a website?

Hopefully one of our C++ gurus can educate both of us about what could be causing this for you.

Well seeing as how the Windows files that deal with memory allocation end in .c not .cpp, I'm assuming that file is part of mIRC, so really Khaled is the only one who can really say what would trigger that assertion.

ok i myself did alil research into this ....... it is infact a windows problem on how is allocates memory ,,,,,, ive done several searches and each one come up with someone reporting it not only for mirc but several other program ..... here is one example url where this is discussed ..... yet i didnt see a solution yet aside form the person saying they corrected it by changing something somewhere but didnt tell what or where .....

Debug Assertion problems

i will continue researching this and see if i can find a solution in my searches ..... altho i dont have this problem ... i just like finding answers LOL

EDIT ADDED FROM HERE DOWN

just found a small lil bit of info about where this code comes from so ill post it here to maybe help someone else who is tryin to find a resolution to this

Well guess I was wrong, all the debug assertions I've seen occur in dbgheap.c, never seen one in dbgdel.cpp. But in any case, it still means Khaled is the only one who can do anything about it. Windows can report the error, but only the application can fix it. Also, considering mIRC doesn't crash too often (at least not for me) and mIRC has no "send debug data to mIRC developers" feature, what is the point of linking against the debug RT? If mIRC doesn't provide a way for users to provide debug information, then all it does is increase the exe size.

oh no i wasnt trying to prove u wrong in any way ... i was simply reseaching and trying to figure this one out and i figured id post the info to see if someone could help with the info i come acrossed ...... dont think i was out to prove u wrong ... i just was hoping maybe with more info someone who knew this stuff could come up with a solution for them

Well heap corruptions are very common and very hard to find. I forget the name of the program, but there was one that had a heap corruption error reported in 1989 and they only fixed it sometime last year. They are easy to create but hard to find. Really, there is no one who can do anything unless they have access to the mIRC code and can setup some memory testing utilities to check it out, and this of course means Khaled is the only one who can do it.

Yeah, if I press ignore at the error screen I get dbgheap.c error. So is there anything I can do to fix this problem?

maybe try uninstalling mIRC and getting a clean copy? or could the prob possibly be something mucked up in windows which in turn effected mIRC since that was the app he opened?
i read several places, and all implied it was a memory allocation prob and/or related to a corrupt dll ... which is why i asked if he had added a dll or script. I see your point re the code, but would help to know if ALT did anything relating to dlls at all about the same time.

ALT: did you? and is mIRC the only app you are having a prob with? What OS? Can you think of anything you did/added just before this happened?

Ill try uninstalling mirc, getting a new download and installing in a different directory making sure not to do anything else during the process. Here is my story though. Maybe 6 months ago on this same computer I had mirc running fine, then I had to reformat my computer. I'm not sure if that helps or anything. If its the "way" I allocate memory, is there a way to allocate the standard way? Also I only had the problem with this program and I'm running W98. Help meh!