Sqlyog Crash

This topic is empty.

Viewing 7 reply threads

Author

Posts
- April 18, 2007 at 1:06 am #10290
  
  Anubuis
  Member
  
  So far SQLyog has crashed on me 7 times attempting to import a sql dump into a database.
  
  Each time it gets farther along on the import.
  
  SQLyog version is: SQLyog Community Edition 6.0 (BETA)
  
  File size that I'm importing is: 275,353 KB.
  
  Only message I get is, SQLyog crashed. dump saved as SQLyog_Dump_002.dmp
  
  Is there anything I can do to prevent this crash?
- April 18, 2007 at 9:51 am #23790
  
  Rohit
  Member
  
  6.0 is still in beta. Can you try the same with 5.29?
  
  Could you send us some sample data to reproduce the test case?
- April 18, 2007 at 12:54 pm #23791
  
  Anubuis
  Member
  
  Rohit wrote on Apr 18 2007, 04:51 AM:
  
  6.0 is still in beta. Can you try the same with 5.29?
  
  Could you send us some sample data to reproduce the test case?
  
  The first time I tried the import was with 5.29
  
  As far as sample data, I'll give you the download link.
  
  SDB for TBC 3478
  
  This is a database for a game server.
  
  But it always crashes on the same file. Never happens on small files.
  
  sdb.sql is the file it crashes on. 218MB is the file size.
- April 18, 2007 at 1:20 pm #23792
  
  adarsh
  Member
  
  Hi,
  
  Please attach the sample sql dump of the database which is crashing.
  
  And also attach the SQLyog crash dump (saved in SQLyog installed folder) so that we can analyze that crash dump and we can find reason for crash.
  
  Quote:
  
  I'll give you the download link.
  
  SDB for TBC 3478
  
  This link is not working there is no sdb.sql file in this link.
  
  Thanks
  
  Adarsh
- April 18, 2007 at 1:26 pm #23793
  
  peterlaursen
  Participant
  
  hello!
  
  we cannot use your link!
  
  please zip and attach a dump here (or you may create a ticket, if you do not want to expose your data).
- April 18, 2007 at 11:05 pm #23794
  
  Anubuis
  Member
  
  Here are the files. If I missed any file, please let me know.
  
  Here is a summary of what I did.
  
  Connect to MySQL with SQLyog
  
  Created a new database
  
  Named it SDB
  
  Right clicked SDB
  
  Selected Restore from SQL Dump.
  
  Around 190800 KBs it crashes. (this number is always different)
  
  I also noticed that my RAM usage is at 97% when the crash happens. (Logitech G15 Keyboard display reading)
  
  I have 2Gbs of Ram incase you are wondering.
  
  I do shut down all unnecessary processes before import.
  
  Anti-viruses are shut down also.
  
  I can not upload the file that crashes SQLyog, it is 9mbs compressed.
  
  Here is a link to the file I uploaded. SDB.SQL.zip
- April 19, 2007 at 10:26 am #23795
  
  adarsh
  Member
  
  Hi,
  
  Thank you for reporting.
  
  Finally we are able to reproduce it.
  
  We will fix this issue in our next release.
  
  Thanks
  
  Adarsh
- April 20, 2007 at 3:07 pm #23796
  
  adarsh
  Member
  
  Hi,
  
  We have identified the problem.
  
  If you enable the “Log Queries in history tab” SQLyog adds every query in the history tab that you execute during the batch process.
  
  But if you have more and more queries, the history tab size also increase and gradually reaches the point of saturation and crashes.
  
  In your case too, the SQL dump is pretty big and so the history tab memory usage increases with every query thats get executed by the batch process and eventually crash at some point of time.
  
  If you uncheck the 'Log Query(s) in History Tab during batch process' option in the Preferences I think it will work smoothly.
  
  So try doing that and let us know the details.
  
  Between, we are also trying to come up with a solution for the same.
  
  Adarsh
Author

Posts