Found segfault issue in splay tree (possibly other trees as well)

[elliotcm]

Hi there.

While using the library (specially the splay tree) as backend to a project, I did a stress test and found my app segfaulting under some strange and very specific conditions (300,000 items added to the tree in one loop followed by another loop of 300,000 items, no problem. 350,000 items added in one loop = segfault).

This is recreatable by loading your benchmarks for the treemaps and changing the array size to 261_123 (or any value above 261,122).

[kanwei]

Thanks for reporting this. Looks like it's blowing the stack with "recursively_mark_nodes". I'll see if I can fix it cleanly.

[kanwei]

Fixed in 98d20f9...

[elliotcm]

Awesome.