[#75225] [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7) — k@...
Issue #12324 has been reported by Kazuki Yamaguchi.
6 messages
2016/04/27
[#78693] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
k@rhe.jp wrote:
[#78701] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Kazuki Yamaguchi <k@...>
2016/12/17
On Sat, Dec 17, 2016 at 01:31:12AM +0000, Eric Wong wrote:
[#78702] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
Kazuki Yamaguchi <k@rhe.jp> wrote:
[ruby-core:75050] [Ruby trunk Bug#12305] "can't remove str from str_id" at unregister_sym
From:
konstantin.starodubtsev@...
Date:
2016-04-20 20:39:13 UTC
List:
ruby-core #75050
Issue #12305 has been updated by Konstantin Starodubtsev. Assignee set to ruby-core ---------------------------------------- Bug #12305: "can't remove str from str_id" at unregister_sym https://bugs.ruby-lang.org/issues/12305#change-58172 * Author: Konstantin Starodubtsev * Status: Open * Priority: Normal * Assignee: ruby-core * ruby -v: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux] * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- I'm experiencing random occurrences of "can't remove str from str_id" crash. Message string looks like this one: /srv/sim/.rvm/gems/ruby-2.3.0@env-manager/gems/mongo-2.2.4/lib/mongo/server/description.rb:508: [BUG] 0x007f4f400ab310 can't remove str from str_id (`..dO.) The only constant thing in it is the "can't remove str from str_id" substring. Other things like address, source code location or symbol string value in brackets differ between crash reports (see attachments). In a C level backtrace information the only common part is top of a trace: -- C level backtrace information ------------------------------------------- /srv/sim/.rvm/rubies/ruby-2.3.0/lib/libruby.so.2.3(rb_vm_bugreport+0x51f) [0x7f4f8b0106ff] vm_dump.c:688 /srv/sim/.rvm/rubies/ruby-2.3.0/lib/libruby.so.2.3(rb_bug+0xcf) [0x7f4f8ae9a01f] error.c:420 /srv/sim/.rvm/rubies/ruby-2.3.0/lib/libruby.so.2.3(unregister_sym.part.12+0x20) [0x7f4f8ae4aada] symbol.c:399 /srv/sim/.rvm/rubies/ruby-2.3.0/lib/libruby.so.2.3(rb_gc_free_dsymbol+0x62) [0x7f4f8afa56a2] symbol.c:637 /srv/sim/.rvm/rubies/ruby-2.3.0/lib/libruby.so.2.3(gc_sweep_step+0x621) [0x7f4f8aec0d01] gc.c:2211 /srv/sim/.rvm/rubies/ruby-2.3.0/lib/libruby.so.2.3(heap_get_freeobj_from_next_freepage+0x72) [0x7f4f8ae498c3] gc.c:3624 /srv/sim/.rvm/rubies/ruby-2.3.0/lib/libruby.so.2.3(newobj_slowpath_wb_protected+0xf4) [0x7f4f8aec43d4] gc.c:1679 We hit this bug at least once per day, so should you need any other information, let me know. Attached are three full [BUG] reports for three different occurrences. ---Files-------------------------------- report-01.log (247 KB) report-03.log (251 KB) report-02.log (266 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>