ruby_memcheck 2.1.0 → 2.1.2

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 5d5d9a9370f2c62f82adb6bccb89e003e7fd42662a3ea786fc6625689e55e85f
4
- data.tar.gz: dc82e568dc90d505363dae4f486c1b2f849141328d0a4326ae7a0d8bfe712739
3
+ metadata.gz: 62852fcef1f92f736c7fb3ac7e32b5246661db102e6177f4c0f0e9ba71ee0fa1
4
+ data.tar.gz: 8c6ea3da941069400b99cf73eb0ea6c881d9a2066486c72169a553ff6bf03e00
5
5
  SHA512:
6
- metadata.gz: 4c0a004789b25d7407fd7ffcacdd3c155e73f1662f7fbeda7d8abc17b79d3dc24d5c7dafe95ee0b35cd48e860eec156293a5cdc1077f86148e979a6fab09144f
7
- data.tar.gz: 06513eb0786d509df597c2efd929050669d8825bb09badd2d2f9d9ec9ee0df9bfa21ce43fbbc34f55d736b2c0eb0d497c96c658a5e7fe93a190633dcfb47bda8
6
+ metadata.gz: ed8c72be6f6753a11f778e72fe036d8f0f7f35214b2b8d94cfb39c7ebab99d2cd443e23b2a4fdc0b5e4f22e4b99a87e74292512ee39180bbb8f7d2a78061eaa6
7
+ data.tar.gz: dc27d11869a745eb873683337c2fb72ebe9995a7c7f2faef76a7b79018b1e936e0b21a1e488b15997fa9909d4177e83316f0891527ecebdc636f09a8dd661eaa
@@ -5,5 +5,18 @@ at_exit do
5
5
  f.write($LOADED_FEATURES.join("\n"))
6
6
  end
7
7
 
8
+ # We need to remove the @_memoized instance variable from Minitest::Spec
9
+ # objects because it holds a hash that contains memoized objects in `let`
10
+ # blocks, this can contain objects that will be reported as a memory leak.
11
+ if defined?(Minitest::Spec)
12
+ require "objspace"
13
+
14
+ ObjectSpace.each_object(Minitest::Spec) do |obj|
15
+ if obj.instance_variable_defined?(:@_memoized)
16
+ obj.remove_instance_variable(:@_memoized)
17
+ end
18
+ end
19
+ end
20
+
8
21
  GC.start
9
22
  end
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module RubyMemcheck
4
- VERSION = "2.1.0"
4
+ VERSION = "2.1.2"
5
5
  end
@@ -60,3 +60,12 @@
60
60
  fun:rb_callable_method_entry
61
61
  ...
62
62
  }
63
+ {
64
+ The date library lazily initializes Regexps using static local variables through the function `regcomp`. The Regexp will end up being reported as a memory leak.
65
+ Memcheck:Leak
66
+ ...
67
+ fun:rb_enc_reg_new
68
+ ...
69
+ fun:date__parse
70
+ ...
71
+ }
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: ruby_memcheck
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.1.0
4
+ version: 2.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Peter Zhu
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2023-08-14 00:00:00.000000000 Z
11
+ date: 2023-08-23 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: nokogiri
@@ -174,7 +174,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
174
174
  - !ruby/object:Gem::Version
175
175
  version: '0'
176
176
  requirements: []
177
- rubygems_version: 3.4.10
177
+ rubygems_version: 3.5.0.dev
178
178
  signing_key:
179
179
  specification_version: 4
180
180
  summary: Use Valgrind memcheck without going crazy