forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Sqlyog Crash
- This topic is empty.
-
AuthorPosts
-
-
March 28, 2012 at 3:09 pm #33225
Mitch
ParticipantA query that returns a row with picture = null does not crash.
-
March 28, 2012 at 4:33 pm #33226
ashwin
MemberHi Mitch,
This is not reproducible in Win 7. This crash report is similar- http://code.google.com/p/sqlyog/issues/detail?id=1764
Please attach the crash dump here. We will investigate into this tomorrow.
Thank you for reporting.
Regards,
Ashwin
-
March 28, 2012 at 4:48 pm #33227Participant
Here is the dump file.
-
March 29, 2012 at 2:57 pm #33228
peterlaursen
Participant@Mitch. The dump does not have a usable stack trace and we cannot reproduce the crash either.
Does it happen consistently on your environment?
Desktop environment? Gnome?
Have you tried to restart the system?
-
March 29, 2012 at 3:13 pm #33229Participant
It happens every time I run that particular query. Here is another dump.
Gnome = yes.
Reboot = tried it.
-
April 2, 2012 at 7:41 am #33230Member
@Mitch, We are unable to reproduce the crash. The dump also does not have a usable stack trace. We had 1M picture in the 'picture' column but “SELECT * from web_object_review WHERE webobjectreviewid=14;” query returned the result without crashing. It could be a data specific issue. So could you share us the table dump(with any client) or the 1MB image so that we could try at our end and reproduce it?
-
April 2, 2012 at 2:00 pm #33231Participant
Attached is dump of a table that exhibits the same problem. It is a copy of the original table containing only the single row that causes the problem.
This statement works fine:
SELECT * FROM mlc2;
This one causes the crash:
SELECT * FROM mlc2 WHERE webobjectreviewid=14;
-
April 3, 2012 at 1:13 pm #33232Participant
It does not crash here. Basically same environment (Ubuntu 10.10 w. Wine 1.2.2).
Any idea?
It could be a memory-handling bug in Wine having only 'fatal effect' if some other program is also running. Maybe you could try with a minimal set of programs running? Also I wonder if you have more systems with same configuration to try with? Or maybe even you could try to remove Wine and reinstall it?
-
April 3, 2012 at 2:04 pm #33233Participant
I've played with some options trying to figure out some more clues. It only crashes when the “EXPLAIN EXTENDED info” box is checked under “Enable Query Profiler”. When “EXPLAIN EXTENDED info” is not checked, the query runs fine. (And it runs fine with “Enable Query Profiler” unchecked.)
Trace from SQL server is shown below.
I can run “EXPLAIN EXTENDED SELECT * FROM mlc2 WHERE webobjectreviewid=14 LIMIT 0, 1000;” by itself OK, both in SQLyog and from the command line.
You might examine the code that parses the result of the EXPLAIN command. The only difference between EXPLAIN and EXPLAIN EXTENDED seems to be the inclusion of the “filtered” column, so you might check the handling of that value. Here is what I get from EXPLAIN EXTENDED on the command line:
mysql> EXPLAIN EXTENDED SELECT * FROM mlc2 WHERE webobjectreviewid=14 LIMIT 0, 1000;
+—-+
+
+
+
+
+
+
+
+
+
+| id | select_type | table | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+—-+
+
+
+
+
+
+
+
+
+
+| 1 | SIMPLE | mlc2 | const | PRIMARY | PRIMARY | 4 | const | 1 | 100.00 | |
+—-+
+
+
+
+
+
+
+
+
+
+Here is the explain for the query that does not crash;
mysql> EXPLAIN EXTENDED SELECT * FROM mlc2 LIMIT 0, 1000 ;
+—-+
+
+
+
+
+
+
+
+
+
+| id | select_type | table | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+—-+
+
+
+
+
+
+
+
+
+
+| 1 | SIMPLE | mlc2 | ALL | NULL | NULL | NULL | NULL | 1 | 100.00 | |
+—-+
+
+
+
+
+
+
+
+
+
+SQL trace from crash:
120403 8:52:17 729 Query SET PROFILING = 1
729 Query SET profiling_history_size = 0
729 Query SET profiling_history_size = 15
729 Query SHOW STATUS
729 Query SELECT * FROM mlc2 WHERE webobjectreviewid=14 LIMIT 0, 1000
729 Query SHOW STATUS
729 Query SHOW PROFILES
729 Query select state, round(sum(duration),5) as `duration (summed) in sec` from information_schema.profiling where query_id = 16 group by state order by `duration (summed) in sec` desc
729 Query SET PROFILING = 0
729 Query EXPLAIN EXTENDED
SELECT * FROM mlc2 WHERE webobjectreviewid=14 LIMIT 0, 1000
729 Query SHOW WARNINGS
-
April 4, 2012 at 5:45 am #33234Member
Thank you for the very useful information. We could reproduce the crash when EXPLAIN EXTENDED is enabled. We are checking this.
-
-
AuthorPosts
- You must be logged in to reply to this topic.
