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

4.0 Enterprise Crashes

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › 4.0 Enterprise Crashes

  • This topic is empty.
Viewing 0 reply threads
  • Author
    Posts
    • December 25, 2004 at 2:57 am #8718
      edw
      Member

      The first hint was a fault:

      Quote:
      Faulting application SQLyogEnt.exe, version 1.0.0.1, faulting module SciLexer.dll, version 1.6.1.0, fault address 0x000323f3.

      while copying from and to Win3003 Std. servers. Restarting, I checked what as happening after copying a couple databases (12M and 292M) from one server to another. With SQLyog's memory use at 643M and 43% of CPU with only a 15kbps transfer rate, the problem was apparent. It became even clearer when restarted the program and copied a small 500k DB. Opening the first connection, memory use was at 6540K; the second connection took it to 6772K; and then copying the little database drove it up to 15.8M. Memory never gets released; each operation just drives consumption higher.

  • Author
    Posts
Viewing 0 reply threads
  • You must be logged in to reply to this topic.