Could not check/invoke the error myself, although the bug is quite probably due to a missing null pointer check. Added this check in trunk revision 12141.
Could not check/invoke the error myself, although the bug is quite probably due to a missing null pointer check. Added this check in trunk revision 12141.