From: nobu@...
Date: 2014-01-22T06:59:51+00:00
Subject: [ruby-core:59965] [ruby-trunk - Bug #9440] [Closed] Calling methods on a `Queue.new.dup` or `Queue.new.clone` causes Segfault

Issue #9440 has been updated by Nobuyoshi Nakada.

Status changed from Open to Closed
% Done changed from 0 to 100

Applied in changeset r44681.

----------
thread/thread.c: no dup

* ext/thread/thread.c (Init_thread): ConditionVariable and Queue
  are not able to copy.  [ruby-core:59961] [Bug #9440]

----------------------------------------
Bug #9440: Calling methods on a `Queue.new.dup` or `Queue.new.clone` causes Segfault
https://bugs.ruby-lang.org/issues/9440#change-44497

* Author: Shannon Skipper
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: lib
* Target version: 
* ruby -v: 2.1.0p0
* Backport: 2.1: UNKNOWN
----------------------------------------
On all platforms with ruby-2.1.0 calling a Queue#method on a duped or cloned Queue results in a Segfault:

    queue = Queue.new.dup
    queue.empty? # Segfault

The same issue occurs when calling other Queue#methods.



-- 
http://bugs.ruby-lang.org/