>It could be a bug but why it shows up for this particular class library?

Without having the source to trace I can't answer that, I have looked in xsource but the builder code doesn't seem to be there.