Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Generally saying, all memory leaks I currently observe on a test load of a single PerDoc topic of Foswiki::Exception documentation are related to use of global variables. Imported Devel::Leak::Object module and adapted it to support Foswiki::Object infrastructure to get correct locations of where objects were created and to keep stacktraces for easy tracking down of leakage causes. Because it's primarily a test-related module included it into UnitTestContrib unfrastructure and called it Unit::Leak::Object. - foswiki_debug.psgi tries to make use of Unit::Leak::Object first and then falls back to Devel::Leak::Object if failed. - QUERY macro object is now using attribute evalParser instead of a global variable $evalParser. - Got rid of BEGIN block in Query::Node. - Added method __orig to Foswiki::Object which locates the exact point where object was created bypassing ::new and ::create methods. - JsonRpcContrib cleans up $SERVER global variable upon destruction.
- Loading branch information