#26 MALLOC_DEBUG anyone?

[Alan Ellis]

It appears that there is some memory corruption in the client.

I grabbed the .9.8 source and compiled it (after fixing some
warnings and errors, but that is another issue), and if I run
it with MALLOC_DEBUG=10 or 15 it pops up some debugger
messages about mem thrashing, it looks to be a heap bug.

I would recommend checking out the Dev Article on MALLOC_DEBUG
=15 from the Be Archives and trying that to find the bug.
Sadly the stack trace for me did not help.

Please contact me directly for further information.

Alan

[Alan Ellis]

Logged In: YES
user_id=235688

I have determined that the problem is actually a NetPositive bug, as
I re-compiled that peice of junk with the memory checking and it
crashed on me all by itself in the -same- way as Scooby was
crashing.

The solution for this would be to fix NetPositive (something that I
just -can't- see Be doing at this time), or perhaps make a replicant
View of Mozilla ... hrm, nothing overly promising here... Perhaps
contanc the NetOptomist guy and see if he is willing to donate his
code/efforts to this?

Alan