You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
diff --git a/src/memwatch.cc b/src/memwatch.cc
index 6ebed41..186887d 100644
--- a/src/memwatch.cc
+++ b/src/memwatch.cc
@@ -60,7 +60,7 @@ static struct
// the period from which this leak analysis starts
time_t leak_time_start;
// the base memory for the detection period
- time_t leak_base_start;
+ size_t leak_base_start;
// the number of consecutive compactions for which we've grown
unsigned int consecutive_growth;
} s_stats;
diff --git a/src/util.cc b/src/util.cc
index 81fcd88..b41a198 100644
--- a/src/util.cc
+++ b/src/util.cc
@@ -10,7 +10,7 @@
#include <stdlib.h> // abs()
std::string
-mw_util::niceSize(int bytes)
+mw_util::niceSize(size_t bytes)
{
std::stringstream ss;
diff --git a/src/util.hh b/src/util.hh
index c7a967b..987f303 100644
--- a/src/util.hh
+++ b/src/util.hh
@@ -7,7 +7,7 @@
namespace mw_util {
// given a size in bytes, return a human readable representation of the
// string
- std::string niceSize(int bytes);
+ std::string niceSize(size_t bytes);
// given a delta in seconds, return a human redable representation
std::string niceDelta(int seconds);
I get the following reason in a
leak
event.With the included patch, it looks better.
This is about a minute after the application starts. The growth was 45305024 bytes, so that's the reason for the high growth rate that is reported.
The text was updated successfully, but these errors were encountered: