[#70977] [Ruby trunk - Feature #11473] Immutable String literal in Ruby 3 — arai@...
Issue #11473 has been updated by Shunichi Arai.
3 messages
2015/10/04
[#71062] [Ruby trunk - Bug #10892] Deadlock in autoload — eregontp@...
Issue #10892 has been updated by Benoit Daloze.
4 messages
2015/10/12
[#71090] Re: [Ruby trunk - Bug #10892] Deadlock in autoload
— Eric Wong <normalperson@...>
2015/10/14
eregontp@gmail.com wrote:
[#71127] [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call — normalperson@...
Issue #11607 has been updated by Eric Wong.
3 messages
2015/10/20
[#71164] [Ruby trunk - Feature #11614] [Open] [RFC] use id_table for constant tables — normalperson@...
Issue #11614 has been reported by Eric Wong.
3 messages
2015/10/22
[#71211] [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call — naruse@...
Issue #11607 has been updated by Yui NARUSE.
6 messages
2015/10/27
[#71212] Re: [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call
— Eric Wong <normalperson@...>
2015/10/27
Yes, user must check if the function is MT-safe. Probably fine
[#71246] Re: [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call
— Aaron Patterson <tenderlove@...>
2015/10/28
On Tue, Oct 27, 2015 at 08:54:07AM +0000, Eric Wong wrote:
[#71254] Re: [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call
— Eric Wong <normalperson@...>
2015/10/28
Aaron Patterson <tenderlove@ruby-lang.org> wrote:
[#71230] [Ruby trunk - Feature #11625] Unlock GVL for SHA1 calculations — tenderlove@...
Issue #11625 has been updated by Aaron Patterson.
5 messages
2015/10/27
[#71236] Re: [Ruby trunk - Feature #11625] Unlock GVL for SHA1 calculations
— Юрий Соколов <funny.falcon@...>
2015/10/28
What's about other hashsum algos? MD5, SHA2, etc
[#71242] Re: [Ruby trunk - Feature #11625] Unlock GVL for SHA1 calculations
— Eric Wong <normalperson@...>
2015/10/28
Юрий Соколов <funny.falcon@gmail.com> wrote:
[#71239] [Ruby trunk - Bug #11384] multi-threaded autoload sometimes fails — shugo@...
Issue #11384 has been updated by Shugo Maeda.
4 messages
2015/10/28
[ruby-core:71231] [Ruby trunk - Bug #11626] [Open] fprintf in c extension keep adding memory usage
From:
guchen.yang@...
Date:
2015-10-27 21:43:54 UTC
List:
ruby-core #71231
Issue #11626 has been reported by GC Yang.
----------------------------------------
Bug #11626: fprintf in c extension keep adding memory usage
https://bugs.ruby-lang.org/issues/11626
* Author: GC Yang
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: 1.9.3p550
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
fprintf will keep adding memory usage without releasing it.
I was doing it in rails console, not sure if it makes any different. The code like this:
VALUE leak (VALUE self, VALUE in) {
char *str = StringValuePtr(in);
char *pstr;
pstr = malloc (10240);
strcat(pstr,str);
fprintf (stdout, pstr);
self = rb_str_new_cstr(pstr);
free (pstr);
return self;
}
void Init_extension(){
rb_define_global_function("leak", leak, 1);
}
100000000.times{leak("lots of garbage")}
without the fprintf line the memory usage is normal, adding that line just keep adding memory, kill the console process will release the memory.
If I do 100000.times{Process.wait(fork{ stuff})}, memory also looks normal. Leaking somewhere????
--
https://bugs.ruby-lang.org/