* [ruby-core:92342] [Ruby trunk Bug#15779] NoMemoryError 後の ensure で ruby が CPU 100% で固まる現象
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
@ 2019-04-20 11:57 ` buzz.taiki
2019-04-20 12:15 ` [ruby-core:92343] " buzz.taiki
` (6 subsequent siblings)
7 siblings, 0 replies; 8+ messages in thread
From: buzz.taiki @ 2019-04-20 11:57 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been reported by buzztaiki (Taiki Sugawara).
----------------------------------------
Bug #15779: NoMemoryError 後の ensure で ruby が CPU 100% で固まる現象
https://bugs.ruby-lang.org/issues/15779
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
以下の再現用コードを実行すると、ruby が CPU 100% で固まってしまいます。
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
不思議なことに、以下のように一度 NoMemoryError を rescue してから raise すると再現しません。
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
ensure 節を `sleep 100` 等にして Ctrl-C を押した場合でも再現するようです。`puts 'XXX'` にした場合では再現しませんでした。
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* [ruby-core:92343] [Ruby trunk Bug#15779] NoMemoryError 後の ensure で ruby が CPU 100% で固まる現象
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
2019-04-20 11:57 ` [ruby-core:92342] [Ruby trunk Bug#15779] NoMemoryError 後の ensure で ruby が CPU 100% で固まる現象 buzz.taiki
@ 2019-04-20 12:15 ` buzz.taiki
2019-04-20 12:40 ` [ruby-core:92344] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU buzz.taiki
` (5 subsequent siblings)
7 siblings, 0 replies; 8+ messages in thread
From: buzz.taiki @ 2019-04-20 12:15 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been updated by buzztaiki (Taiki Sugawara).
Sorry, I wote bug report in Japanese to ruby-core.
In English:
Subject: After NoMemoryError, ruby freezes and takes 100% CPU
Description:
Run following reproduce code, ruby freezes and takes 100% CPU.
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
But interestingly, the following code does not reproduce this issue.
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
It was also reproduced when put `sleep 100` in ensure clause. But `puts 'XXX'` does not reproduce it.
----------------------------------------
Bug #15779: NoMemoryError 後の ensure で ruby が CPU 100% で固まる現象
https://bugs.ruby-lang.org/issues/15779#change-77688
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
以下の再現用コードを実行すると、ruby が CPU 100% で固まってしまいます。
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
不思議なことに、以下のように一度 NoMemoryError を rescue してから raise すると再現しません。
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
ensure 節を `sleep 100` 等にして Ctrl-C を押した場合でも再現するようです。`puts 'XXX'` にした場合では再現しませんでした。
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* [ruby-core:92344] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
2019-04-20 11:57 ` [ruby-core:92342] [Ruby trunk Bug#15779] NoMemoryError 後の ensure で ruby が CPU 100% で固まる現象 buzz.taiki
2019-04-20 12:15 ` [ruby-core:92343] " buzz.taiki
@ 2019-04-20 12:40 ` buzz.taiki
2019-04-29 1:36 ` [ruby-core:92471] " buzz.taiki
` (4 subsequent siblings)
7 siblings, 0 replies; 8+ messages in thread
From: buzz.taiki @ 2019-04-20 12:40 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been updated by buzztaiki (Taiki Sugawara).
I rewrote this issue to English.
----------------------------------------
Bug #15779: After NoMemoryError, ruby freezes and takes 100% CPU
https://bugs.ruby-lang.org/issues/15779#change-77690
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Run following reproduce code, ruby freezes and takes 100% CPU.
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
But interestingly, the following code does not reproduce this issue.
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
It was also reproduced when put `sleep 100` in ensure clause, run it and hit Ctrl-C. But `puts 'XXX'` does not reproduce it.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* [ruby-core:92471] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
` (2 preceding siblings ...)
2019-04-20 12:40 ` [ruby-core:92344] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU buzz.taiki
@ 2019-04-29 1:36 ` buzz.taiki
2019-04-29 1:37 ` [ruby-core:92472] " buzz.taiki
` (3 subsequent siblings)
7 siblings, 0 replies; 8+ messages in thread
From: buzz.taiki @ 2019-04-29 1:36 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been updated by buzztaiki (Taiki Sugawara).
File strace.txt added
In this situation, I want ruby to finish GC quickly or to crash.
In my production code, this issue has been avoided by not creating huge objects and by using rescue and re-raise.
I attach strace log (`strace -ttt -o strace.txt ruby a.rb`).
It seems to cause loop of `Resource temporarily unavailable`.
```
...
1556496315.537693 read(6, 0x55794d88b333, 5) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538029 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538245 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538404 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538524 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538612 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538682 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538751 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538820 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538889 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.538958 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.539027 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.539094 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.539161 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.539320 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.539401 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
1556496315.539470 read(4, 0x7ffeaf4b5f40, 8) = -1 EAGAIN (Resource temporarily unavailable)
...
```
----------------------------------------
Bug #15779: After NoMemoryError, ruby freezes and takes 100% CPU
https://bugs.ruby-lang.org/issues/15779#change-77819
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Run following reproduce code, ruby freezes and takes 100% CPU.
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
But interestingly, the following code does not reproduce this issue.
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
It was also reproduced when put `sleep 100` in ensure clause, run it and hit Ctrl-C. But `puts 'XXX'` does not reproduce it.
---Files--------------------------------
strace.txt (377 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* [ruby-core:92472] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
` (3 preceding siblings ...)
2019-04-29 1:36 ` [ruby-core:92471] " buzz.taiki
@ 2019-04-29 1:37 ` buzz.taiki
2019-04-30 3:52 ` [ruby-core:92486] " s.wanabe
` (2 subsequent siblings)
7 siblings, 0 replies; 8+ messages in thread
From: buzz.taiki @ 2019-04-29 1:37 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been updated by buzztaiki (Taiki Sugawara).
I test this reproduction code at ruby 2.5.5 (ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux]). In this version, this issue is not reproduced (ruby is not frozen).
```
~/opt/ruby/2.5.5/bin/ruby a.rb
#<StringIO:0x0000560b317f53b8 @base_uri=#<URI::HTTPS https://www.ruby-lang.org/>, @meta={"server"=>"Cowboy", "strict-transport-security"=>"max-age=31536000", "content-type"=>"text/html", "etag"=>"W/\"91e880089832f50e7e7bf1371600cc60\"", "x-frame-options"=>"SAMEORIGIN", "via"=>"1.1 vegur, 1.1 varnish", "content-length"=>"424", "accept-ranges"=>"bytes", "date"=>"Mon, 29 Apr 2019 01:11:21 GMT", "age"=>"1800", "connection"=>"keep-alive", "x-served-by"=>"cache-hnd18749-HND", "x-cache"=>"HIT", "x-cache-hits"=>"1", "x-timer"=>"S1556500281.267699,VS0,VE6", "vary"=>"Accept-Encoding"}, @metas={"server"=>["Cowboy"], "strict-transport-security"=>["max-age=31536000"], "content-type"=>["text/html"], "etag"=>["W/\"91e880089832f50e7e7bf1371600cc60\""], "x-frame-options"=>["SAMEORIGIN"], "via"=>["1.1 vegur", "1.1 varnish"], "content-length"=>["424"], "accept-ranges"=>["bytes"], "date"=>["Mon, 29 Apr 2019 01:11:21 GMT"], "age"=>["1800"], "connection"=>["keep-alive"], "x-served-by"=>["cache-hnd18749-HN
D"], "x-cache"=>["HIT"], "x-cache-hits"=>["1"], "x-timer"=>["S1556500281.267699,VS0,VE6"], "vary"=>["Accept-Encoding"]}, @status=["200", "OK"]>
Traceback (most recent call last):
a.rb: failed to allocate memory (NoMemoryError)
```
----------------------------------------
Bug #15779: After NoMemoryError, ruby freezes and takes 100% CPU
https://bugs.ruby-lang.org/issues/15779#change-77820
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Run following reproduce code, ruby freezes and takes 100% CPU.
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
But interestingly, the following code does not reproduce this issue.
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
It was also reproduced when put `sleep 100` in ensure clause, run it and hit Ctrl-C. But `puts 'XXX'` does not reproduce it.
---Files--------------------------------
strace.txt (377 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* [ruby-core:92486] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
` (4 preceding siblings ...)
2019-04-29 1:37 ` [ruby-core:92472] " buzz.taiki
@ 2019-04-30 3:52 ` s.wanabe
2019-04-30 6:32 ` [ruby-core:92487] " s.wanabe
2019-05-16 17:07 ` [ruby-core:92685] " buzz.taiki
7 siblings, 0 replies; 8+ messages in thread
From: s.wanabe @ 2019-04-30 3:52 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been updated by wanabe (_ wanabe).
I think it is from r58380.
before r58380, `rb_memerror` calls `rb_longjmp` via `rb_exc_raise` and clear raised_flag.
But now `rb_memerror` keeps raised_flag and just calls `EC_JUMP_TAG`.
`rb_threadptr_execute_interrupts` should raise `Interrupt` exception on hitting ctrl-c,
but just return immediately because `th->raised_flag` is truthy.
I've confirmed above behavior with the script to use `miniruby`.
```
begin
"a" * 10000000000
ensure
Thread.new(Thread.current) do |t|
Thread.pass
t.raise Interrupt
sleep 0.01
STDERR.puts "shutting down..."
Process.kill :KILL, $$
end
sleep
end
```
----------------------------------------
Bug #15779: After NoMemoryError, ruby freezes and takes 100% CPU
https://bugs.ruby-lang.org/issues/15779#change-77831
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Run following reproduce code, ruby freezes and takes 100% CPU.
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
But interestingly, the following code does not reproduce this issue.
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
It was also reproduced when put `sleep 100` in ensure clause, run it and hit Ctrl-C. But `puts 'XXX'` does not reproduce it.
---Files--------------------------------
strace.txt (377 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* [ruby-core:92487] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
` (5 preceding siblings ...)
2019-04-30 3:52 ` [ruby-core:92486] " s.wanabe
@ 2019-04-30 6:32 ` s.wanabe
2019-05-16 17:07 ` [ruby-core:92685] " buzz.taiki
7 siblings, 0 replies; 8+ messages in thread
From: s.wanabe @ 2019-04-30 6:32 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been updated by wanabe (_ wanabe).
How about this?
```
diff --git a/vm.c b/vm.c
index 41064f07c3..be394b0dae 100644
--- a/vm.c
+++ b/vm.c
@@ -1895,7 +1895,7 @@ vm_exec(rb_execution_context_t *ec, int mjit_enable_p)
}
else {
result = ec->errinfo;
- rb_ec_raised_reset(ec, RAISED_STACKOVERFLOW);
+ rb_ec_raised_reset(ec, RAISED_STACKOVERFLOW | RAISED_NOMEMORY);
while ((result = vm_exec_handle_exception(ec, state, result, &initial)) == Qundef) {
/* caught a jump, exec the handler */
result = vm_exec_core(ec, initial);
```
----------------------------------------
Bug #15779: After NoMemoryError, ruby freezes and takes 100% CPU
https://bugs.ruby-lang.org/issues/15779#change-77832
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Run following reproduce code, ruby freezes and takes 100% CPU.
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
But interestingly, the following code does not reproduce this issue.
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
It was also reproduced when put `sleep 100` in ensure clause, run it and hit Ctrl-C. But `puts 'XXX'` does not reproduce it.
---Files--------------------------------
strace.txt (377 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [ruby-core:92685] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
` (6 preceding siblings ...)
2019-04-30 6:32 ` [ruby-core:92487] " s.wanabe
@ 2019-05-16 17:07 ` buzz.taiki
7 siblings, 0 replies; 8+ messages in thread
From: buzz.taiki @ 2019-05-16 17:07 UTC (permalink / raw)
To: ruby-core
Issue #15779 has been updated by buzztaiki (Taiki Sugawara).
Thank you for your reply!
In my environment, this patch with ruby 2.6.3 has been fixed this issue (ruby was not frozen)!!
```
~/opt/ruby/bug15779_v2_6_3_fix/bin/ruby ~/tmp/a.rb
#<StringIO:0x000055914e06fda8 @base_uri=#<URI::HTTPS https://www.ruby-lang.org/>, @meta={"server"=>"Cowboy", "strict-transport-security"=>"max-age=31536000", "content-type"=>"text/html", "etag"=>"W/\"91e88008983
2f50e7e7bf1371600cc60\"", "x-frame-options"=>"SAMEORIGIN", "via"=>"1.1 vegur, 1.1 varnish", "content-length"=>"424", "accept-ranges"=>"bytes", "date"=>"Thu, 16 May 2019 17:04:03 GMT", "age"=>"1082", "connection"=>"keep-alive", "x-served-by"=>"cache-hnd18751-HND", "x-cache"=>"HIT", "x-cache-hits"=>"1", "x-timer"=>"S1558026243.322961,VS0,VE0", "vary"=>"Accept-Encoding"}, @metas={"server"=>["Cowboy"], "strict-transport-security"=>["max-age=31536000"], "content-type"=>["text/html"], "etag"=>["W/\"91e880089832f50e7e7bf1371600cc60\""], "x-frame-options"=>["SAMEORIGIN"], "via"=>["1.1 vegur", "1.1 varnish"], "content-length"=>["424"], "accept-ranges"=>["bytes"], "date"=>["Thu, 16 May 2019 17:04:03 GMT"], "age"=>["1082"], "connection"=>["keep-alive"], "x-served-by"=>["cache-hnd18751-HND"], "x-cache"=>["HIT"], "x-cache-hits"=>["1"], "x-timer"=>["S1558026243.322961,VS0,VE0"], "vary"=>["Accept-Encoding"]}, @status=["200", "OK"]>
Traceback (most recent call last):
/home/taiki/tmp/a.rb: failed to allocate memory (NoMemoryError)
```
```
cat ~/tmp/a.rb
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
----------------------------------------
Bug #15779: After NoMemoryError, ruby freezes and takes 100% CPU
https://bugs.ruby-lang.org/issues/15779#change-78045
* Author: buzztaiki (Taiki Sugawara)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Run following reproduce code, ruby freezes and takes 100% CPU.
```
require 'open-uri'
begin
"a" * 10000000000
ensure
p open('https://www.ruby-lang.org/')
end
```
But interestingly, the following code does not reproduce this issue.
```
require 'open-uri'
begin
begin
"a" * 10000000000
rescue NoMemoryError
raise
end
ensure
p open('https://www.ruby-lang.org/')
end
```
It was also reproduced when put `sleep 100` in ensure clause, run it and hit Ctrl-C. But `puts 'XXX'` does not reproduce it.
---Files--------------------------------
strace.txt (377 KB)
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-05-16 17:07 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <redmine.issue-15779.20190420115757@ruby-lang.org>
2019-04-20 11:57 ` [ruby-core:92342] [Ruby trunk Bug#15779] NoMemoryError 後の ensure で ruby が CPU 100% で固まる現象 buzz.taiki
2019-04-20 12:15 ` [ruby-core:92343] " buzz.taiki
2019-04-20 12:40 ` [ruby-core:92344] [Ruby trunk Bug#15779] After NoMemoryError, ruby freezes and takes 100% CPU buzz.taiki
2019-04-29 1:36 ` [ruby-core:92471] " buzz.taiki
2019-04-29 1:37 ` [ruby-core:92472] " buzz.taiki
2019-04-30 3:52 ` [ruby-core:92486] " s.wanabe
2019-04-30 6:32 ` [ruby-core:92487] " s.wanabe
2019-05-16 17:07 ` [ruby-core:92685] " buzz.taiki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).