chockfull of useful information. And even better, he’s put together two great
engine has similar functionality, which you can turn on by typing about:config
Lint detects more types of errors and is configurable. To give it a try,
I ran it over the MapBuzz code base and was very impressed by the errors it revealed.
I immediately added it to our automated testing processes (i.e., its spawned
by a rake task
now) and have come to depend on it.
And if that wasn’t enough, Matthias has adopted a second tool, called Drip,
leaks occur in IE because it uses COM based
reference counting to delete objects. Reference counting is
fast, and easy to understand, but does not handle
references. As you use your website in IE, Drip keeps track of these circular
references. Once you’re done, it prints out a report showing you where the
memory leaks occurred.
Thanks for the great tools Matthias.