Bug #8336

Segfault in :=~

Added by Sam Saffron 12 months ago. Updated 12 months ago.

[ruby-core:54609]
Status:Closed
Priority:High
Assignee:-
Category:-
Target version:-
ruby -v:2.0.0 p0 Backport:2.0.0: UNKNOWN

Description

Just had this happen a few times, seems to be GC related, releasing memory pressure worked around it.

https://gist.github.com/SamSaffron/5471044


Related issues

Duplicates ruby-trunk - Bug #8100: Segfault in trunk Closed 03/15/2013

History

#1 Updated by Nobuyoshi Nakada 12 months ago

  • Status changed from Open to Closed

Seems same as #8100.

Also available in: Atom PDF