Jump to content


Photo

Sqlyog Crash


  • Please log in to reply
10 replies to this topic

#1 Mitch

Mitch

    Advanced Member

  • Members
  • PipPipPip
  • 74 posts
  • Gender:Male

Posted 28 March 2012 - 02:51 PM

Ubuntu 10.10 64 bit
Wine 1.2.2
SQLyog Ultimate 9.63
mysql: 5.1.61-0ubuntu0.10.10.1

SQLyog crashes when executing this query:
SELECT * from web_object_review WHERE webobjectreviewid=14;

Dump is in C:\windows\profiles\mclaborn\Application Data\SQLyog\SQLyog_Dump_002.dmp.

Is it safe to post the dump file here?

Definition of that table is below. webobjectreviewid=14 does have a 1M picture in the 'picture' column.

CREATE TABLE `web_object_review` (
`webobjectreviewid` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'ID of this record',
`webobjectid` int(10) unsigned NOT NULL COMMENT 'which web object is reviewed',
`name` varchar(100) NOT NULL COMMENT 'customer name',
`emailaddress` varchar(255) DEFAULT NULL COMMENT 'customer email address',
`city` varchar(100) NOT NULL COMMENT 'customer city',
`state` varchar(4) DEFAULT NULL COMMENT 'customer state',
`message` longtext NOT NULL COMMENT 'review text',
`webimageid` int(10) unsigned DEFAULT NULL COMMENT 'ID of web image, if approved',
`approvalstatus` enum('I','N','Y') NOT NULL DEFAULT 'I' COMMENT 'approval status, I = initial',
`processeddatetime` datetime DEFAULT NULL COMMENT 'when the review was done',
`addeddatetime` datetime NOT NULL COMMENT 'when the record was created',
`picture_filetype` varchar(20) DEFAULT NULL COMMENT 'file type of picture, if any',
`picture` longblob COMMENT 'picture bytes, if any',
PRIMARY KEY (`webobjectreviewid`),
KEY `FK_web_object_review_object` (`webobjectid`),
CONSTRAINT `FK_web_object_review_object` FOREIGN KEY (`webobjectid`) REFERENCES `web_object` (`webobjectid`)
) ENGINE=InnoDB AUTO_INCREMENT=7097 DEFAULT CHARSET=latin1;

#2 Mitch

Mitch

    Advanced Member

  • Members
  • PipPipPip
  • 74 posts
  • Gender:Male

Posted 28 March 2012 - 03:09 PM

A query that returns a row with picture = null does not crash.

#3 ashwin

ashwin

    Advanced Member

  • Members
  • PipPipPip
  • 275 posts
  • Gender:Male
  • Location:Bangalore, India

Posted 28 March 2012 - 04:33 PM

Hi Mitch,

This is not reproducible in Win 7. This crash report is similar- http://code.google.c.../detail?id=1764
Please attach the crash dump here. We will investigate into this tomorrow.

Thank you for reporting.

Regards,
Ashwin

#4 Mitch

Mitch

    Advanced Member

  • Members
  • PipPipPip
  • 74 posts
  • Gender:Male

Posted 28 March 2012 - 04:48 PM

Here is the dump file.

Attached Files



#5 peterlaursen

peterlaursen

    Advanced Member

  • Admin
  • PipPipPip
  • 7,869 posts
  • Gender:Male
  • Location:Skagen, Denmark
  • Interests:well ... jazz/folk music, photography, chess, nature, ecology, history, bicycling, Highland Malts ... well, Lowland Malts and Cognac too actually :-) just wonder how I get the time to touch a computer! SQLyog and MONyog? no that's not interest, that's BASIC NEEDS simply!

Posted 29 March 2012 - 02:57 PM

@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?


Computers make your grey hair come off ....

Peter Laursen
Webyog

#6 Mitch

Mitch

    Advanced Member

  • Members
  • PipPipPip
  • 74 posts
  • Gender:Male

Posted 29 March 2012 - 03:13 PM

It happens every time I run that particular query. Here is another dump.

Gnome = yes.

Reboot = tried it.

Attached Files



#7 ashwin

ashwin

    Advanced Member

  • Members
  • PipPipPip
  • 275 posts
  • Gender:Male
  • Location:Bangalore, India

Posted 02 April 2012 - 07:41 AM

@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?

#8 Mitch

Mitch

    Advanced Member

  • Members
  • PipPipPip
  • 74 posts
  • Gender:Male

Posted 02 April 2012 - 02:00 PM

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;

Attached Files



#9 peterlaursen

peterlaursen

    Advanced Member

  • Admin
  • PipPipPip
  • 7,869 posts
  • Gender:Male
  • Location:Skagen, Denmark
  • Interests:well ... jazz/folk music, photography, chess, nature, ecology, history, bicycling, Highland Malts ... well, Lowland Malts and Cognac too actually :-) just wonder how I get the time to touch a computer! SQLyog and MONyog? no that's not interest, that's BASIC NEEDS simply!

Posted 03 April 2012 - 01:13 PM

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?
Computers make your grey hair come off ....

Peter Laursen
Webyog

#10 Mitch

Mitch

    Advanced Member

  • Members
  • PipPipPip
  • 74 posts
  • Gender:Male

Posted 03 April 2012 - 02:04 PM

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

#11 ashwin

ashwin

    Advanced Member

  • Members
  • PipPipPip
  • 275 posts
  • Gender:Male
  • Location:Bangalore, India

Posted 04 April 2012 - 05:45 AM

Thank you for the very useful information. We could reproduce the crash when EXPLAIN EXTENDED is enabled. We are checking this.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users