I noticed a few problems in the SQL editor area, and using the MySQL plugin with the Statement Separator set to ";".
Clicking the next and previous SQL buttons causes the cursor to jump between the first section of the query and the second based upon a blank line (double \n\n), not the ";" character from an opened sql text file (simplified example below)
When attempting to run a sql statement such as:
WHERE col1 > 11
-- AND col3 IS('not used')
AND col2 < 22
The full statement up to the ";" is not sent, resulting in a large number of result data to be returned causing an out of memory exception as the latter clauses are not sent.
I'm not sure where the DB specific Statement Separator is used, but it seems to be just using the BaseSQLEntryPanel SQL_STMT_SEP of two line breaks..