Bug #51588 | Viewing log files from MySQL Workbench causes random crashes | ||
---|---|---|---|
Submitted: | 28 Feb 2010 17:02 | Modified: | 4 Apr 2010 13:06 |
Reporter: | David White | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S2 (Serious) |
Version: | 5.2.16 | OS: | Windows (XP sp3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Logs tab fails, MySQL Workbench |
[28 Feb 2010 17:02]
David White
[4 Mar 2010 13:06]
Susanne Ebrecht
Which server version are you using? Do you store the logs in files or tables?
[4 Mar 2010 13:36]
David White
I am saving the logs to the mysql table. Server version 5.5.2 m2 community. Windows XP sp3. Although the same crash happens when they are saved to files. from the my.ini [client] port=3306 [mysql] default-character-set=latin1 log-output = TABLE general-log log-queries-not-using-indexes log-short-format log-warnings log-output = TABLE general-log log-queries-not-using-indexes log-short-format log-warnings log-output = TABLE log-queries-not-using-indexes log-warnings log-short-format general-log [mysqld] # The TCP/IP Port the MySQL Server will listen on port=3306 #Path to installation directory. All paths are usually resolved relative to this. basedir="C:/Program Files/MySQL/MySQL Server 5.5/" #Path to the database root datadir="C:/Documents and Settings/All Users/Application Data/MySQL/MySQL Server 5.5/Data/" default-storage-engine=INNODB max_connections=100 query_cache_size=0 table_cache=256 tmp_table_size=9M myisam_max_sort_file_size=100G myisam_sort_buffer_size=18M key_buffer_size=11M read_rnd_buffer_size=256K sort_buffer_size=256K innodb_additional_mem_pool_size=2M innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 4M innodb_buffer_pool_size=18M innodb_log_file_size=10M innodb_thread_concurrency=8 max_allowed_packet = 16M innodb log-output = TABLE log-queries-not-using-indexes log-short-format log-warnings general-log expire_logs_days = 2
[4 Apr 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".