Skip to content
  • Anushree Prakash B's avatar
    186fbc85
    Bug#28977428 - TERMINATE CALLED AFTER THROWING AN INSTANCE · 186fbc85
    Anushree Prakash B authored
                   OF 'STD::BAD_ALLOC'
    
    DESCRIPTION:
    ============
    Large number of rows in the performance_schema.data_locks
    table results in std::bad_alloc exception being thrown and
    terminating the program.
    
    ANALYSIS:
    ========
    Reading rows from the data_locks or data_lock_waits table
    can return an unbounded number of rows during a scan,
    depending on the application payload, as some user sessions
    may have an unbounded number of records locked.
    This can cause severe memory spike, which in turn can take
    the server down if not handled properly.
    
    FIX:
    ====
    Exception handling has been added while reading
    performance_schema.data_locks table and
    performance_schema.data_lock_waits table such that it fails
    with an error.
    
    RB: 21314
    186fbc85
    Bug#28977428 - TERMINATE CALLED AFTER THROWING AN INSTANCE
    Anushree Prakash B authored
                   OF 'STD::BAD_ALLOC'
    
    DESCRIPTION:
    ============
    Large number of rows in the performance_schema.data_locks
    table results in std::bad_alloc exception being thrown and
    terminating the program.
    
    ANALYSIS:
    ========
    Reading rows from the data_locks or data_lock_waits table
    can return an unbounded number of rows during a scan,
    depending on the application payload, as some user sessions
    may have an unbounded number of records locked.
    This can cause severe memory spike, which in turn can take
    the server down if not handled properly.
    
    FIX:
    ====
    Exception handling has been added while reading
    performance_schema.data_locks table and
    performance_schema.data_lock_waits table such that it fails
    with an error.
    
    RB: 21314
Loading