389-ds ns-slapd crashes when searched on memberUid>=X when memberUid is indexed

This is seen with both
389-ds-base-1.2.11.15-46-el6.x86_64 and 389-ds-base-1.2.11.15-50-el6_6.x86_64

ns-slapd[15663]: segfault at 18cb000018e3 ip 00000033fa277f3a sp 00007fc516bf6000 error 4 in libc-2.12.so[33fa200000+189000]

memberUid is indexed like the following:

cn=memberUid,cn=index,cn=userRoot,cn=ldbm_database,cn=plugins,dc=config
objectClass: top
objectClass: nsIndex
cn: memberUid
nsIndexType: eq
nsIndexType: pres
nsIndexType: sub
nsSystemIndex: false

Query: ldapsearch -h localhost -x -LLL -b ou=groups,dc=XX,dc=YY,dc=com 'memberUid>=A' --- causes the crash
ldapsearch -h localhost -x -LLL -b dc=XX,dc=YY,dc=com 'memberUid>=A' -- works fine
ldapsearch -h localhost -x -LLL 'memberUid>=A' -- works fine
ldapsearch -h localhost -x -LLL -b ou=groups,dc=XX,dc=YY,dc=com '(&(objectclass=posixGroup)(memberUid>=A))' --- works fine
There is no index corruption.

I understand that the query doesn't make sense, but i would atleast expect ns-slapd not segfault/crash.