RADPHE v0.06 Beta Build 002

Lightweight: dont $_INTIN['Dump'][FILE]= do your own dBug and call it smartly on the part of the array you want not the whole thing.
Heavyweight in ram... do the opposite of what i said. But there are sanity checks now... it will not likely fail and it will try to show you what changed when you wanted to dump something because it went wrong.

OK, so filtering globals and fatty memory tracking areas of memory is not working.
because it ends up being by reference to globals and you cant clone everything.
cant test=globals and then test/globals/globals=null even.
SO sanity check is imposed.
It will remember the finishing state of last event for compare to the current finishing state of a event level include.
BUT the last is only if it is under 100mb, then THIS event will compare if less than 250mb ram.
You could at present hit 300mb ram.
this is also because the output from dbug is so big. then history is fully implemented you will have a iframe into a new call that pulls saved work from session or db.
keeping output buffers from bloating.
then if i get array copy filters working and maybe my own array diff...
it should get back to being light weight; and it is if your not debugging.