|
From: Gerd W. <ger...@t-...> - 2020-11-07 20:58:47
|
You may post SQuirreL's logs. Here are the steps - Close SQuirreL - Go to the logs directory of your SQuirreL user dir - Delete or move away all existing log files (this is to prevent sending unnecessary big log files). - Open and Close SQuirreL - Send the log file that was newly created. Gerd Am 07.11.20 um 04:06 schrieb info: > Tried downgrading the JDK down to 1.8.40 - no difference. > Tried disabling all drivers - no difference. I cannot delete aliases but > without drivers they have nothing to load, have they? > > I solved the memory problem by adding -Xmx256M argument to the bat file, > but the 15 second start hang and 30 second shutdown hang are still there > - no difference. > > I could email logs if something could be gleaned from them. Lots of > exceptions in them. > > > > On 2020-11-06 07:01 PM, info wrote: >> I am currently on the most recent available download for Windows, it's >> 4... something as of 2x days ago. It behaves the same as 3.9, whether >> I run one or another. >> >> Like I said, I've already tried to remove Sqlite: >> >> > I tried to unload SQLite but it did not change anything. >> >> This means that I deleted Sqlite alias and removed the extra classpath >> from the driver config, rendering it (X) in the list. >> >> I distinctly remember having to pass Java command line argument to >> allow memory over 256 MB or something along these lines. How can it >> load more without me passing that parameter? If it matters, I am on >> JDK 1.8.121 which is the same one where I had to pass the argument. >> >> The loading screen gets stuck on loading JDBC drivers. On closing the >> app, it hangs for 30 seconds and then asks to save any open files. >> Once told to save or not, it shuts down instantaneously. >> >> Is there any trace log? >> >> >> On 2020-11-06 02:24 PM, Gerd Wagner wrote: >>> Sorry, I can't reproduce your problem using >>> https://github.com/xerial/sqlite-jdbc/releases/tag/3.32.3.2 >>> which is latest today. ;) >>> >>> Could you give some more details? >>> >>> Here are some things you may try: >>> - Delete all SQLite Aliases. >>> - Remove the SQLite driver from SQuirreL's driver definition. Either >>> by deleting its "Extra Class Path" entry (recommended way to use a >>> driver) or by removing it from SQuirreL's lib directory (NOT the >>> recommended way to use a driver). Anyway after this the driver >>> definition should appear unchecked (red crossed) in your drivers list. >>> >>> Gerd >>> >>> Am 06.11.20 um 12:53 schrieb info: >>>> Hi all, >>>> >>>> A long-time Squirrel user here. Up until now I never had any issues. >>>> Been using mostly versions up to 3.9 with all kinds of databases for >>>> years. Currently I am working on a project that connects to every >>>> imaginable database, and I have the following JDBC drivers loaded: >>>> >>>> DB2 JDBC-SQLJ 10.5 >>>> >>>> iSeries JTOpen 7.10 >>>> >>>> JTDS 1.3.1 >>>> >>>> MySQL connector 5.1.40 >>>> >>>> PostgreSQL 9.4.12 >>>> >>>> SQLite whatever latest is today. >>>> >>>> I am almost positive that until I loaded SQLite, the startup and >>>> shutdown times were reasonable, within a few seconds. Since I loaded >>>> it, everything changed. It now takes up to 20 seconds to start the >>>> app and up to 30-40 seconds for it to shut down. It starts up with >>>> 800 MB of RAM allocated and grows to about 1.1 GB over the course of >>>> me running a handful of queries that return a handful of records >>>> from a couple of those back ends, no more than 1-2 back ends at a >>>> time. I never run anything that returns huge datasets. >>>> >>>> I tried to unload SQLite but it did not change anything. >>>> >>>> Since the machine that I am developing on is constrained on RAM (8 >>>> GB) and I have to run local Oracle tuned to use only 1 GB, DB2, MS >>>> SQL also tuned to use up to 1 GB, and Postgress, the memory >>>> utilization of Squirrel has become a considerable annoyance. I do >>>> not recall it ever using more than 256 MB of RAM without specifying >>>> Java command line option in the past. I am certainly not passing the >>>> memory option to Java to increase memory allocation. So it is a >>>> mystery what is going on. >>>> >>>> I unloaded almost all plugins but there was very small difference in >>>> memory utilization. The UI has changed to vanilla AWT so it seems, >>>> and it is kind of nimbler to respond, but the overall problem remains. >>>> >>>> Any ideas? >>>> >>>> Thanks for your help! >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Squirrel-sql-users mailing list >>>> Squ...@li... >>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users >>> >> >> >> >> >> _______________________________________________ >> Squirrel-sql-users mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users >> > > > > > _______________________________________________ > Squirrel-sql-users mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
