Bug #48458: simple query tries to allocate enormous amount of
memory The server was doing a bad class typecast causing setting of wrong value for the maximum number of items in an internal structure used in equality propagation. Fixed by not doing the wrong typecast and asserting the type of the Item where it should be done.
Showing
Please register or sign in to comment