Back to bug 1317076

Who When What Removed Added
Vít Ondruch 2016-03-14 11:56:38 UTC Component rh-ruby22 ruby
Joe Orton 2016-03-14 12:29:42 UTC CC jorton
Deepu K S 2016-03-16 10:34:13 UTC CC dkochuka
Deepu K S 2016-04-01 09:23:10 UTC CC kanderso
Flags needinfo?(kanderso)
Deepu K S 2016-05-02 16:26:28 UTC Flags needinfo?(vondruch)
Deepu K S 2016-05-02 16:26:56 UTC Flags needinfo?(kanderso)
Vít Ondruch 2016-05-03 06:22:40 UTC Flags needinfo?(vondruch)
Alan Matsuoka 2016-05-16 14:58:50 UTC CC alanm
Steve Almy 2016-05-16 15:17:43 UTC Priority unspecified high
CC bgollahe, salmy
Flags needinfo?(bgollahe)
Brian Gollaher 2016-05-16 19:25:50 UTC CC briang
Flags needinfo?(bgollahe) needinfo+
Lenka Špačková 2016-05-18 14:12:02 UTC CC lkuprova
Jun Aruga 2016-06-09 10:41:17 UTC Status NEW ASSIGNED
CC jaruga
Assignee vondruch jaruga
Jun Aruga 2016-06-14 14:54:37 UTC CC pvalena
Jun Aruga 2016-06-22 10:13:12 UTC Depends On 1348918
Jun Aruga 2016-06-23 08:28:08 UTC Status ASSIGNED MODIFIED
errata-xmlrpc 2016-06-23 08:43:20 UTC Status MODIFIED ON_QA
Jun Aruga 2016-06-28 10:05:07 UTC Doc Text Cause:
Object allocation was forbidden in the garbage collection phase of Ruby.
But it could happen for the issue, and Ruby crashed.

Consequence:
One guy found the issue when he/she ran RSpec test suite program.
After that, several people reported its issue with their development environment information.
The condition to reproduce it, is not clear.

Fix:
It was fixed on Ruby 2.2.3 on upstream.
I used the patch used to fix this issue on the upstream.

Result:
I could not reproduce by myself, though it passed the test suite.
So, I would like for our customer who reported this, to use this fixed version.
Jun Aruga 2016-06-28 10:06:05 UTC Doc Text Cause:
Object allocation was forbidden in the garbage collection phase of Ruby.
But it could happen for the issue, and Ruby crashed.

Consequence:
One guy found the issue when he/she ran RSpec test suite program.
After that, several people reported its issue with their development environment information.
The condition to reproduce it, is not clear.

Fix:
It was fixed on Ruby 2.2.3 on upstream.
I used the patch used to fix this issue on the upstream.

Result:
I could not reproduce by myself, though it passed the test suite.
So, I would like for our customer who reported this, to use this fixed version.
Cause: Object allocation was forbidden in the garbage collection phase of Ruby. But it could happen for the issue, and Ruby crashed.

Consequence: One guy found the issue when he/she ran RSpec test suite program. After that, several people reported its issue with their development environment information.
The condition to reproduce it, is not clear.

Fix: It was fixed on Ruby 2.2.3 on upstream.
I used the patch used to fix this issue on the upstream.

Result: I could not reproduce by myself, though it passed the test suite. So, I would like for our customer who reported this, to use this fixed version.
Vít Ondruch 2016-06-28 10:59:10 UTC Doc Text Cause: Object allocation was forbidden in the garbage collection phase of Ruby. But it could happen for the issue, and Ruby crashed.

Consequence: One guy found the issue when he/she ran RSpec test suite program. After that, several people reported its issue with their development environment information.
The condition to reproduce it, is not clear.

Fix: It was fixed on Ruby 2.2.3 on upstream.
I used the patch used to fix this issue on the upstream.

Result: I could not reproduce by myself, though it passed the test suite. So, I would like for our customer who reported this, to use this fixed version.
Cause: Object allocation is forbidden during the garbage collection phase of Ruby. If it happens, the Ruby process ends with error.

Consequence: When executing specific code, it might happen that object allocation is triggered during garbage collection phase. In this specific case, the global symbol table hash object comparison triggered allocation of additional object.

Fix: The global symbol hash table now uses key comparison using their identities instead comparison by key values, which avoids allocation of addition objects during garbage collection phase and therefor it fixes this issue.

Result: This issue was acknowledged by upstream bug https://bugs.ruby-lang.org/issues/10933 and fixed in Ruby 2.2.3. This fix was backported and confirmed to fix the original issue reported.
Lenka Špačková 2016-06-28 12:41:31 UTC Doc Text Cause: Object allocation is forbidden during the garbage collection phase of Ruby. If it happens, the Ruby process ends with error.

Consequence: When executing specific code, it might happen that object allocation is triggered during garbage collection phase. In this specific case, the global symbol table hash object comparison triggered allocation of additional object.

Fix: The global symbol hash table now uses key comparison using their identities instead comparison by key values, which avoids allocation of addition objects during garbage collection phase and therefor it fixes this issue.

Result: This issue was acknowledged by upstream bug https://bugs.ruby-lang.org/issues/10933 and fixed in Ruby 2.2.3. This fix was backported and confirmed to fix the original issue reported.
Object allocation is forbidden during the garbage collection phase of Ruby. Previously, the global symbol hash table used comparison by key values, which could allocate a new object during the garbage collection phase. This consequently led to termination of the Ruby process. With this update, the global symbol hash table uses key comparison by identity instead, which does not allocate an additional object. As a result, no additional objects are allocated during the garbage collection phase.
Iveta Wiedermann 2016-07-07 14:15:02 UTC CC isenfeld
QA Contact qe-baseos-apps isenfeld
Iveta Wiedermann 2016-07-08 08:33:55 UTC Flags needinfo?(jaruga)
Jun Aruga 2016-07-08 09:08:55 UTC Flags needinfo?(jaruga)
Iveta Wiedermann 2016-07-20 13:35:34 UTC Flags needinfo?(jaruga)
Jun Aruga 2016-07-20 14:23:25 UTC Flags needinfo?(jaruga)
Iveta Wiedermann 2016-07-21 07:15:56 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-07-21 11:44:04 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-07-25 08:48:13 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-07-25 04:48:13 UTC

Back to bug 1317076