Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Sqlyog 5.11 Buffer Overrun

forums forums SQLyog SQLyog: Bugs / Feature Requests Sqlyog 5.11 Buffer Overrun

  • This topic is empty.
Viewing 10 reply threads
  • Author
    Posts
    • #9632
      advantis
      Member

      I upgraded from the free SQLyog 5.02 to the free SQLyog 5.11. SQLyog 5.02 had a bug with timestamps and default field value (CURRENT_TIMESTAMP is sent surrounded by single quotes which sets the field to 0000-00-00 00:00:00 instead of NOW()) and I upgraded to see if it's still present. I can't test its presence though because SQLyog 5.11 won't start on my system. It displays the nag screen, I click the 3rd option, then I get this:

      Code:
      Microsoft Visual C++ Runtime Library
      Program: C:Program FilesSQLyogSQLyog.exe
      A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must be terminated now.

      Is my system really broken and I should attempt a Windows installation, or is there something wrong with SQLyog? I didn't see others complain, so I lean to my system having a problem, but I thought I'd let you guys know anyway.

      For the moment, I downgraded back to 5.02.

    • #21318
      peterlaursen
      Participant

      There was a similar report with an early beta:

      http://www.webyog.com/forums/index.php?sho…=buffer+overrun

      It is very hard to tell what happens here as it is a rare issue. We could not reproduce. There may be a memory handling bug that only takes effect in very special situations/on very special systems.

      You can install 5.11 to a different folder. Try that. And try closing down as many unneeded background processes as possible. Also try starting the program as the first thing after reboot.

      What is your OS?

      If there is an issue it shall be fixed, but we simply need more info to spot it then. You are using the free version, so it is not related to auto-complete. That is important to know.

      BTW: I can assure you that the issue with CURRENT_TIMESTAMP is fixed:

      http://webyog.com/faq/8_99_en.html

    • #21319
      Haugland
      Member

      I'm having this problem as well.

      It occurs in both the free version and the Enterprise Trial version immediately after start-up. In the free version, it occurs after I click the 'nag' screen, just prior to showing the form to select the database to work on.

      I'm running Windows XP Professional. My memory usage is quite low before running SQLyog, so I think it's safe to rule out a low memory issue — though memory handling is still fair game. I've also tried installing to a couple different folders.

    • #21320
      Marc
      Member

      I just upgraded to 5.11 Enterprise and i get the same problem now too. When starting, a window is opened but closed instantly again. That's it. No error message or anything.

      I removed it completly and reinstalled (even to a different drive/folder) but the error is still there.

    • #21321
      Ritesh
      Member
      Quote:
      I just upgraded to 5.11 Enterprise and i get the same problem now too. When starting, a window is opened but closed instantly again. That's it. No error message or anything.

      Thanks for your bug report and we are working diligently to solve it.

      Can you tell me three things:

      1.) Are you working as a non-admin user?

      2.) Can you open up the sqlyog.ini from the SQLyog installation folder and set AutoComplete=0 under [GENERALPREF] section and try again?

      3.) Were some existing Personal folder files were present from the old installation?

    • #21322
      Ritesh
      Member

      v5.12 BETA has been released. It is now linked with the static library which was used in all pre-5.11 released.

      For more info: http://www.webyog.com/forums/index.php?sho…st=0&#entry9810

    • #21323
      Haugland
      Member

      This beta has appeared to resolve the issue. Thank you!

      I'll report any additional instances of it crashing or having a buffer overrun.

    • #21324
      peterlaursen
      Participant

      We have allready another report where it did not. So on some systems it does and others it does not.

      But people having this isuue could try both .. until the thing is finally fixed.

    • #21325
      Marc
      Member
      Ritesh wrote on Apr 24 2006, 03:17 PM:
      1.) Are you working as a non-admin user?

      2.) Can you open up the sqlyog.ini from the SQLyog installation folder and set AutoComplete=0 under [GENERALPREF] section and try again?

      3.) Were some existing Personal folder files were present from the old installation?

      Hi, I got it running now.

      First i'm working as an admin user. But the second point got me to solve this problem:

      When I opened sqlyog.ini I found it was empty (0 byte size). I don't know how it was after installing it with an old version still installes because I removed the old version and reinstalled the new one before. Since there was nothing in sqlyog.ini and it seemed to me there should be something in, I removed (better I renamed) the ini file. And after that Version 5.11 worked and is now asking for specifying a connection on start up.

      Maybe this is the same with some others here who have this problem.

    • #21326
      peterlaursen
      Participant

      Thanks for your report …

      This was a new variation, I think! You can look around in the Forums and find other variations.

      I tried if an empty sqlyog.ini would crash 5.11 and 5.12 BETA3 on my system and it does not. If there is an empty (or no) sqlyog.ini SQLyog writes this:

      [HSplitter]

      Left=0

      Right=0

      Top=0

      Bottom=0

      ULeftOrTopPercent=0

      [VSplitter]

      Left=0

      Right=0

      Top=0

      Bottom=0

      ULeftOrTopPercent=0

      [SQLYOG]

      Left=0

      Top=0

      Right=600

      Bottom=600

      .. and next displays the connection screen. If you save details here they are saved too and main program window opens.

      From the information from another user we have seen a crash occur after the creation of the sqlyog.ini -file (as an empty file) and before writing anything to it.

      Hmmm.

      Empty sqlyog.ini's, empty 'favorites' folder, favorites-files with an empty extension can crash some systems. Every time we come back to the file system.

    • #21327
      Ritesh
      Member
Viewing 10 reply threads
  • You must be logged in to reply to this topic.