From 277dae3c1a908941b4bb518e60d3ad98f668ccdb Mon Sep 17 00:00:00 2001
From: Felix Ostmann <felix.ostmann@thewar.de>
Date: Tue, 16 Jun 2015 09:06:42 +0200
Subject: [PATCH] "Memleak" in test-script for memleak ...

OK, this is not really a memleak, but the $mech-object keeps a history up to 8675309 entries and for normal sites this can get huge!
-> for testing memleaks we don't need the $mech history
---
 Leak-Hunting/eg/01.pod        | 1 +
 Leak-Hunting/loop_requests.pl | 1 +
 2 files changed, 2 insertions(+)

diff --git a/Leak-Hunting/eg/01.pod b/Leak-Hunting/eg/01.pod
index be5bc48..ed3249e 100644
--- a/Leak-Hunting/eg/01.pod
+++ b/Leak-Hunting/eg/01.pod
@@ -52,6 +52,7 @@ only work on Linux due to checking /proc for the memory usage.
 
     my $mech = Test::WWW::Mechanize::PSGI->new(
         app => $app,
+        stack_depth => 0,
     );
 
     my $start_mem = get_mem();
diff --git a/Leak-Hunting/loop_requests.pl b/Leak-Hunting/loop_requests.pl
index 0b592db..2a22d5a 100644
--- a/Leak-Hunting/loop_requests.pl
+++ b/Leak-Hunting/loop_requests.pl
@@ -10,6 +10,7 @@
 
 my $mech = Test::WWW::Mechanize::PSGI->new(
     app => $app,
+    stack_depth => 0,
 );
 
 my $start_mem = get_mem();