Slow startup under WinXP SP3

J

JimmyM

Member
Under WinXP SP2, PL/SQL Dev would start very quickly. However, this weekend I updated to SP3. Now it takes 27 seconds for the login window to appear. I'm running version 7.1.5-1398.
I re-installed PL/SQL dev before writing this. Performance was unchanged.
CPU usage doesn't spike, nor does HDD usage.
My hardware is a Quad Core 2.4GHz, 4GB RAM (3GB reported by OS).
Any thoughts?
 
Can you go to Help > Support Info, press the 'Copy all pages' button on this info screen, and paste this text into an e-mail reply?
 
Has there been any solution on this issue ?
I have the same problem after updating to SP3, but the startup time is not 27 seconds, but a few minutes.
 
Nothing yet. I've un-installed SP3 and installed the SP3 blocker from Microsoft. Microsoft is pushing SP3 by Automatic update.
 
between 5 and 8 seconds first off, then about 2 seconds for subsequent openings...

2.2GHz, 2GB memory. nothing flash.
 
I tried it at home yesterday with no network at all and there it started up very fast. Enabling the network seemed to slow down the startup, but I haven't tested this very much.
Today, at work it is back to taking minutes to start up. I am in a domain at work, so maybe it has to do something with that.
 
My machine is a member of a domain as well. However, when I'm working from home, I'm not on that domain.
 
I managed to fix my problem by creating a new profile in Windows.
I logged in as another account, moved my directory in c:\Document and Settings\ to another name and logged in again.
With this new profile, PL/SQL Developer starts up quickly again.
I am slowly adding every setting I had back again, so the problem can still return, but so far so good.
 
I had a similar issue with my antivirus (AVG). Their newest release will tell you, during installation, to apply a Windows patch when you don't have it installed. This patch is not included in SP3, and is not listed on recommended/optional lists in Windows Update. It should fix a 15-to-20-second lag on certain calls.

Regards,
Gustavo
 
A just upgraded from latest v7 to v8 and PL/SQL developer needs almoast 20 seconds to open. Second instance opens a bit faster (say 15 seconds).

I have XP SP2 (had problems with SP3 and needed to rollback).

No load on CPU, just long wait.

Program is installed for all profiles, not just one.

Pentium IV 3.4Ghz. No antivirus installed.

 
To obtain some more diagnostic information, can you modify the shortcut and add the debugsql parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debugsql

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory.
 
I reverted to version 7 because I usually open PL/SQL dev. instances up to 50 times per day.

However the problem now persists in version 7 too, but it takes a bit less time - from 10 to 12 seconds.

Here is debug.txt contents. I ran the command at 12:57:00. Debug.txt repors only times 12 seconds later.

PL/SQL Developer
Version 7.1.5.1398
Windows XP Professional 5.1 Build 2600 (Service Pack 2)

Physical memory : 2.095.596 kB (1.346.464 available)
Paging file : 4.194.304 kB (4.194.304 available)
Virtual memory : 2.097.024 kB (2.030.320 available)

Parameters
C:\Program Files\PLSQL Developer\plsqldev.exe
debugsql

Preferences
Session mode: Multi
OCI Library:
Use OCI7: False

Preference Files

Plug-Ins

12.10.2009 12:57:12 Application started
12.10.2009 12:57:12 InitPreferences
12.10.2009 12:57:12 Load C:\Program Files\PLSQL Developer\Preferences\Default = 0
12.10.2009 12:57:12 PreferenceSet.Load C:\Program Files\PLSQL Developer\Preferences\Default\Default.ini
12.10.2009 12:57:12 PreferenceSet.Load OK
12.10.2009 12:57:12 Determine LocalPrefPath
12.10.2009 12:57:12 [1]: C:\Program Files\PLSQL Developer\Preferences
12.10.2009 12:57:12 LocalPrefPath: C:\Program Files\PLSQL Developer\Preferences\matjazc
12.10.2009 12:57:12 Load C:\Program Files\PLSQL Developer\Preferences\matjazc = 0
12.10.2009 12:57:12 PreferenceSet.Load C:\Program Files\PLSQL Developer\Preferences\matjazc\default.ini
12.10.2009 12:57:12 PreferenceSet.Load OK
12.10.2009 12:57:12 PreferenceSet.Load C:\Program Files\PLSQL Developer\Preferences\matjazc\user.prefs
12.10.2009 12:57:12 PreferenceSet.Load OK
12.10.2009 12:57:12 InitPreferences end
12.10.2009 12:57:12 SortPreferenceSets
12.10.2009 12:57:12 - Default matjazc
12.10.2009 12:57:12 - System Default
12.10.2009 12:57:12 pfReadRegistry(PL/SQL Developer\Shell\Open\Command, )
12.10.2009 12:57:12 ReadString OK
12.10.2009 12:57:12 pfReadRegistry: "C:\Program Files\PLSQL Developer\plsqldev.exe" "%1"
12.10.2009 12:57:12 LoadPreferences
12.10.2009 12:57:12 LoadPreferences searching for default
12.10.2009 12:57:12 C:\Program Files\PLSQL Developer\Preferences\matjazc\default.ini
12.10.2009 12:57:12 LoadPreferences NewPref := nil
12.10.2009 12:57:12 LoadPreferences
12.10.2009 12:57:12 LoadPreferences Reading preferences
12.10.2009 12:57:12 pfReadRegistry(PL/SQL Developer\Shell\Open\Command, )
12.10.2009 12:57:12 ReadString OK
12.10.2009 12:57:12 pfReadRegistry: "C:\Program Files\PLSQL Developer\plsqldev.exe" "%1"
12.10.2009 12:57:12 LoadPreferences ReadPosition
12.10.2009 12:57:12 LoadPreferences ToolsBrowserItemClick(nil)
12.10.2009 12:57:12 LoadPreferences CreateBrowserFilters...
12.10.2009 12:57:12 LoadPreferences Files
12.10.2009 12:57:12 LoadPreferences Logon
12.10.2009 12:57:12 LoadPreferences Buttons
12.10.2009 12:57:12 LoadPreferences Printer
12.10.2009 12:57:12 LoadPreferences BrowserFolders
12.10.2009 12:57:12 LoadPreferences
12.10.2009 12:57:12 LoadPreferences end
12.10.2009 12:57:12 MacroLibFilename: C:\Program Files\PLSQL Developer\Macro\matjazc.lib
 
The issue apparently occurs even before PL/SQL Developer is started. You may want to check what your default printer is. Maybe it's not available or on a slow network?
 
Default printer is avaiable.
The problem started since upgrade to v8 and now persists also in v7.
But before upgrade (when v7 was already installed), an attempt to install SP3 was made and restore afterward. I think it has something to do with Windows SP.
However I don't know why only PL/SQL developer starts slow and all other programs respond well as before.

Perhaps creating new user account and fresh PL/SQL installation would fix this (as one of the members confirmed to work), but this is not an option since I am on a domain.
 
You must log in or register to reply here.
Back
Top