[#70252] Re: [ruby-cvs:58640] nobu:r51492 (trunk): node.c: NODE_ALLOCA for ALLOCV — Eric Wong <normalperson@...>
Besides possible backwards compatibility, can we drop volatile
3 messages
2015/08/05
[#70257] [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI — ko1@...
Issue #11420 has been reported by Koichi Sasada.
11 messages
2015/08/06
[#70337] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/11
Nice. Thank you guys for looking into this.
[#70349] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
Btw, did you consider using flexible array to avoid extra malloc
[#70355] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Юрий Соколов <funny.falcon@...>
2015/08/12
I thought to suggest to embed hash_id_table directly into places when it is
[#70356] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— SASADA Koichi <ko1@...>
2015/08/12
On 2015/08/13 4:29, Юрий Соколов wrote:
[#70358] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
SASADA Koichi <ko1@atdot.net> wrote:
[#70509] [Ruby trunk - Misc #11276] [RFC] compile.c: convert to use ccan/list — ko1@...
Issue #11276 has been updated by Koichi Sasada.
3 messages
2015/08/21
[#70639] the undefined behavior of an iterator if it is modified inside of the block to which it yields — Daniel Doubrovkine <dblock@...>
(this is my first time e-mailing list list, so apologies for any misstep :)
4 messages
2015/08/31
[ruby-core:70313] [Ruby trunk - Bug #11411] Crash in rb_gc_mark() during Rails app boot with GC.stress=1
From:
nagachika00@...
Date:
2015-08-10 16:32:39 UTC
List:
ruby-core #70313
Issue #11411 has been updated by Tomoyuki Chikanaga. The fixes are backported into `ruby_2_2` branch at r51521 (for #11352). ---------------------------------------- Bug #11411: Crash in rb_gc_mark() during Rails app boot with GC.stress=1 https://bugs.ruby-lang.org/issues/11411#change-53735 * Author: Ben Weintraub * Status: Closed * Priority: Normal * Assignee: * ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- When booting a newly-initialized Rails 4.2.1 app under Ruby 2.2.2 with `GC.stress` enabled, I get a repeatable crash. The same crash happens at least as far back as 2.1.4 (haven't tried any earlier versions). Steps to reproduce: 1. gem install rails -v 4.2.1 2. rails new stress 3. cd stress 4. bundle 5. echo 'GC.stress = 1' >config/initializers/000_stress.rb 6. bundle exec rails s Expected results: The application should not crash. Actual results: The app crashes with a `SIGABRT` and the message seen below. For convenience, I've attached a tarball of a Rails app built using the above steps that can reproduce this issue. I'm running on Mac OS X 10.10.4, haven't tried with other OSes. ~~~ $ be rails s => Booting WEBrick => Rails 4.2.3 application starting in development on http://localhost:3000 => Run `rails server -h` for more startup options => Ctrl-C to shutdown server /Users/ben/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/mime.rb:55: [BUG] rb_gc_mark(): 0x007f94ebce3c18 is T_NONE (snip) Abort trap: 6 ---Files-------------------------------- stressapp.tar.gz (12.3 KB) ruby_2015-08-02-120653_koan.crash (25.1 KB) bug-11411.log (123 KB) -- https://bugs.ruby-lang.org/