Bug #41944 | "edit table data" not working, "Query Browser" not working | ||
---|---|---|---|
Submitted: | 8 Jan 2009 6:46 | Modified: | 12 Jan 2009 13:25 |
Reporter: | Jiabao Deng | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Administrator | Severity: | S1 (Critical) |
Version: | 1.2.15 | OS: | Windows (Vista SP1) |
Assigned to: | CPU Architecture: | Any | |
Tags: | edit table data, mysql administrator, not working, query browser, regression |
[8 Jan 2009 6:46]
Jiabao Deng
[8 Jan 2009 6:55]
Jiabao Deng
Description: Whenever I right click on a table of a database, and select the second option "edit table data", The "MySQL Administrator" creates a new process "MySQLQueryBrowser.exe" (I know this because I've been checking the "Task Manager") and nothing more. It doesn't respond. It doesn't give any window for me to actually edit table data, nor does it give any error message. Note that the new hanging process is taking 100% CPU resource all the time. Also I found whenever I click on the "Query Browser", it responds the same way - new process hanging and nothing else. OS: Windows Vista SP1 running with administrator MySQL: community server 5.1 MySQL GUI Tools: for 5.0 Hope this can be verified officially. How to repeat: Open any database, right click on any table and select the second option "edit table data". For the "Query Browser", just try to open the "Query Browser" from "MySQL Administrator". Suggested fix: none
[8 Jan 2009 7:30]
Valeriy Kravchuk
Thank you for a bug report. On my XP SP3 VS's debugger catches incorrect memory address access of Query Browser, but essentially the problem is the same, as Administrator tries to start Query Browser again and again, it seems.
[12 Jan 2009 13:25]
Mike Lischke
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Duplicate of Bug #41415