unexpected forestdb iterator behavior

ForestDB iterator created with start key:

0x73, 0x37, 0x35, 0x34, 0x36, 0x32, 0x34, 0xff

with options:

FDB_ITR_NO_DELETES | FDB_ITR_SKIP_MAX_KEY

does not see the key:

0x73, 0x37, 0x35, 0x34, 0x36, 0x32, 0x34, 0xff, 0x00, 0x00, 0x00

Even though it should sort higher (when memcmp of common portion is 0, length is consulted).

I posted about there here:

https://groups.google.com/d/msg/forestdb/iwgOs0kV5-U/KEjVXAjaBAAJ

and Jung-Sang confirmed he saw the same behavior if WAL is manually flushed before iterator_init()