# 1.8.1 YAML emit bug? (Win32)

**URL:** <https://rubytalk.org/t/1-8-1-yaml-emit-bug-win32/11589>\
**Category:** ruby-talk\
**Created:** [17 May 2004 20:06 UTC](https://rubytalk.org/t/1-8-1-yaml-emit-bug-win32/11589 "2004-05-17T20:06:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Austin\_Ziegler](https://avatars.discourse-cdn.com/v4/letter/a/b2d939/32.png) [@Austin\_Ziegler](https://rubytalk.org/u/Austin_Ziegler)\
**Post date:** [17 May 2004 20:06 UTC](https://rubytalk.org/t/1-8-1-yaml-emit-bug-win32/11589/1 "2004-05-17T20:06:50Z")

</div>

Apologies if this has been noted before; I am currently using the 1.8.1  
installer released on 2004.04.26, so this may well be fixed.

irb(main):004:0\> a = “”; (0…8191).each { |i| a \<\< “%c” % [65 + i % 25]  
}; puts a.size; a.to\_yaml; nil  
8191  
=\> nil  
irb(main):005:0\> a = “”; (0…8192).each { |i| a \<\< “%c” % [65 + i % 25]  
}; puts a.size; a.to\_yaml; nil  
8192

The former line works. The latter locks up tighter than the Bush  
Administration’s lips to the American public. I think that if it’s any  
larger than 8192, it causes an access violation/segfault.

-austin

> **···**
>
> –  
> austin ziegler \* [austin.ziegler@evault.com](mailto:austin.ziegler@evault.com)

---

<div class="post-metadata">

**Author:** ![why\_the\_lucky\_stiff1](https://avatars.discourse-cdn.com/v4/letter/w/898d66/32.png) [@why\_the\_lucky\_stiff1](https://rubytalk.org/u/why_the_lucky_stiff1)\
**Post date:** [17 May 2004 20:29 UTC](https://rubytalk.org/t/1-8-1-yaml-emit-bug-win32/11589/2 "2004-05-17T20:29:11Z")

</div>

Austin Ziegler wrote:

> irb(main):005:0\> a = “”; (0…8192).each { |i| a \<\< “%c” % [65 + i % 25]  
> }; puts a.size; a.to\_yaml; nil  
> 8192

Yeah, this is healed in the latest. Ran tests up to (0…8191313) and  
still worked good. Anyone who can test a stable snapshot on Windows?

\_why