MySQL Bugs: #5358: List Index out of bounds (1)

Bug #5358	List Index out of bounds (1)
Submitted:	2 Sep 2004 0:48	Modified:	1 Dec 2004 13:44
Reporter:	Neil Jackson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:	1.07-beta	OS:	Windows (WinXP Pro (SP1+))
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
Had this same crash happen with 1.06alpha, but that time, it happened when I was trying to save or reload a query, I think.

However, this time, it happened when I was trying to save the results of a query out as HTML. I got as far as selecting 'Export Resultset>>Export as HTML', but before the file-save dialog box came up, I got this modal dialog alert saying "The following Exception occurred: List index out of bounds(1)".

The really crazy thing is that dialog box popped up in an endless loop - spawning them at the rate of several per second. I was able to drag a few around and take a screenshot this time, before finally having to kill the app with Task Manager before it ate up all my resources. The pic should be attached with this bug report somewhere... :)

How to repeat:
Really not sure - sorry. This is only the 2nd time I've had it happen, and the preamble was completely different.

Modal Mayhem!

Attachment: mysql-query-browser-crash01..gif (image/gif, text), 51.59 KiB.

Have just noticed from my own screenshot... there does appear to be an error window from the Resultset:Export?? process, or something. It's partly obscured by the modal windows that I moved around, sorry. But in any case, the bulk of its text was not visible, because it's behind the central modal boxes and they're impossible to close quick enough to get back to the bottom one and read it.

Perhaps you can glean something from what you can see of the error message anyway?

Erk... sorry - have just noticed that I do indeed have the output HTML file on my machine, therefore it MUST have reached the file-save dialog step, and I typed in a filename (without an extension, and I notice it has correctly created a file with that name and an .html extension, as you'd expect).

Moreover, the output file does seem complete, and correct.

The reason for the crash seems yet more elusive, then! Sorry!