memory-leak 0.10.1 → 0.10.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 61f53a3abeb664b0d47bc2d889e6fe1b34ce2a29baa5695142efd967598e05a3
-  data.tar.gz: 68f58dcab4789dd5ca02f8e15d4123cefd4ca5fde5e589d5fdaf19681713bd27
+  metadata.gz: ce86ec1f5824a2cafd31ca3765df1967fa8d2226ef88e0479cf0fca07df91cb9
+  data.tar.gz: 3bcaf2a418112277e98de7f81bc7991fedf14e475e9e0801e9a962a567db31aa
 SHA512:
-  metadata.gz: f60866beb7f8d7c2202992442581ce94dd0a5d3b313a4275d2f1073552292c754d481bec364173953d7e53700175f3050efc1b14426ae8292e2a1e549b0d6c3c
-  data.tar.gz: ffcc71882d4f318acce9eab8e516831f8969b4919cb5ac2a762488a782f41501229ada6794429d5e1419f858ee8e40944cb6bf8859997986080fb3e1c06f5412
+  metadata.gz: 8dd4aba9d1e9d835697c809540d28c72ccb2eb901993ec967621740293bf37fd7b20d3d8daf1641dde087d90539b51f63ad8f2bc194d0c0d4a98664ed64f5d1e
+  data.tar.gz: 3a0a336dbfb32bc00d904519ccef29f38c3a10398b1dc17c6f4cc98860e02b7740e5903dbfc1507f371e70d83750ae067e83e004bd2049264bff21be10159a66

checksums.yaml.gz.sig

@@ -1,2 +1,3 @@
-����0��d���
-91�Z��>ś�fZ�nP�<��+�B��������e&�32�`"a-v�&Z��`�X,�����Q����:�w�D٤`S���,w�#b�D�:t
+�KdE�K�W��L�Y���޾�o�~V'��GlL���Ʃ.���v���v	�6��>)�~��r�@��Z���[#����j�5����c]�����R���B-��+;�5�{fye_�f#�
+���IȠ��H0�)�Z��_ۥ��Z�\�R eTH��c���&��Ò�T
&���]�h�h>�o�.@�@���D��'@�c�g�b/�}'���JG ��g����V����`*7�r0G�Z
+��O�m���ڷ�7J�B����L��������ÈK�c�J,ֶ��h��X��7vl���I������.����/�ވ1��r�1�}�E�֝��x��}��BW��bXݹ�"�}����^��cw�@�d�rI<�R�};�

data/lib/memory/leak/monitor.rb

@@ -18,11 +18,6 @@ module Memory
 			# True memory leaks will eventually hit this threshold_size, while small fluctuations will not.
 			DEFAULT_THRESHOLD_SIZE = 1024*1024*10
 			
-			# We track the last N process size increases.
-			# If the process size is not stabilizing within the specified increase_limit, we can assume there is a leak.
-			# With a default interval of 10 seconds, this will track the last ~3 minutes of process size increases.
-			DEFAULT_INCREASE_LIMIT = 20
-			
 			# Create a new monitor.
 			#
 			# @parameter process_id [Integer] The process ID to monitor.
@@ -30,7 +25,7 @@ module Memory
 			# @parameter maximum_size_limit [Numeric | Nil] The maximum process size allowed, in bytes, before we assume a memory leak.
 			# @parameter threshold_size [Numeric] The threshold for process size increases, in bytes.
 			# @parameter increase_limit [Numeric] The limit for the number of process size increases, before we assume a memory leak.
-			def initialize(process_id = Process.pid, maximum_size: nil, maximum_size_limit: nil, threshold_size: DEFAULT_THRESHOLD_SIZE, increase_limit: DEFAULT_INCREASE_LIMIT)
+			def initialize(process_id = Process.pid, maximum_size: nil, maximum_size_limit: nil, threshold_size: DEFAULT_THRESHOLD_SIZE, increase_limit: nil)
 				@process_id = process_id
 				
 				@sample_count = 0

data/lib/memory/leak/version.rb

@@ -5,6 +5,6 @@
 
 module Memory
 	module Leak
-		VERSION = "0.10.1"
+		VERSION = "0.10.2"
 	end
 end

data/readme.md

@@ -14,6 +14,10 @@ Please see the [project documentation](https://socketry.github.io/memory-leak/)
 
 Please see the [project releases](https://socketry.github.io/memory-leak/releases/index) for all releases.
 
+### v0.10.2
+
+  - Disable default `increase_limit: nil`.
+
 ### v0.10.0
 
   - Introduce `free_size_minimum` to monitor minimum free memory size, which can be used to trigger alerts or actions when available memory is critically low.

data/releases.md

@@ -1,5 +1,9 @@
 # Releases
 
+## v0.10.2
+
+  - Disable default `increase_limit: nil`.
+
 ## v0.10.0
 
   - Introduce `free_size_minimum` to monitor minimum free memory size, which can be used to trigger alerts or actions when available memory is critically low.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: memory-leak
 version: !ruby/object:Gem::Version
-  version: 0.10.1
+  version: 0.10.2
 platform: ruby
 authors:
 - Samuel Williams