Lazarus slow to launch...

[1HuntnMan]

Lately, when I startup Lazarus (Win 11 computer), I can see the forms popping up but then it hangs for 30 secs. and then the rest of the project will launch.  Is there a setting I need to fix or change?

[Martin_fr]

Not aware of any settings.

First guess would have been AntiVirus => but if you already see first forms, then AV already let the IDE start, so not sure why it would stop it again.
(unless you only see the splash screen, and you use "startlazarus" which shows the splash, and then loads the actual lazarus.exe)

There shouldn't be any DLL, except if you have packages (like DB stuff) installed, that depends on some dll.

Does that happen when the IDE starts with a new empty project? Or maybe its some file (some very large file) in the project that gets re-opened when you launch the IDE?

You could check the log, start the IDE with "lazarus.exe --debug-log=c:\path\log_name.txt". Or better compile the IDE with -WC  (Tools > Configure build Lazarus), then it will open with a "dos window", and you can watch any log msgs live. So you can see what gets logged when. Maybe there is a clue in that.

[cdbc]

Hi
How many extra packages have you got installed in the Lazarus IDE?
Regards Benny

[Warfley]

Also, first launch or also subsequent launches? Like if Lazarus is already open and you open a second instance, is it also slow? And if you open close and re-open?

[1HuntnMan]

Just launched Lazarus and it took about 25 seconds according to my wrist watch.  Only extra components I have installed is JuijiboDB, LazReport and Jvcl DB.  I'm more suspect of Winders 11 at the moment from your comments.  Usually when I startup the computer whether from sleep or from completely off, I launch Laz first. Tomorrow morning, I'm going to launch Winders and wait 10 minutes before launching Laz.  I'm also going to spend some time later just looking for stuff that's loading that seems to creep into Winders that's totally uneccesary esp. launching Task Manager ... thanks

[440bx]

I suggest you use Process Explorer or System Monitor (formerly Process Hacker) to see what is happening during the Lazarus launch.   

It's quite likely that Defender is the cause of the slow launch and that is instantly visible in either one of those utilities in the CPU utilization and even more in the number of megabytes read.  Anything that does a lot of I/O is going to cause a noticeable slowdown.

[Martin_fr]

Only extra components I have installed is JuijiboDB, LazReport and Jvcl DB. 

I don't know them...
Could they be trying to connect to the DB in the background? And especially if the DB server is not running, and it will wait for a timeout....

First make sure its not the project that is being opened (e.g. if it has components of those packages on the form, and they trigger that).
Worst case they try to connect, even if they are not used by the project.

Of course, it could be something else.

[n7800]

Maybe you can try running Lazarus with your antivirus completely disabled (Windows Defender)? Don't add files or processes to the exceptions, as I've seen some nuances, and rules may be ignored.

[JanRoza]

If you have many reports in your project your projects resource file can become big and the bigger the resource file gets the longer the loading of the project may be. At least that's what I experience in some of my projects.

[d2010]

Lately, when I startup Lazarus (Win 11 computer), I can see the forms popping up but then it hangs for 30 secs. and then the rest of the project will launch.  Is there a setting I need to fix or change?

Please , please you forced win11Lazarus only you have enough experienced with
  multiple compilator/s of Pascal (eg0 delphi7, tp, delphi2009, delplhiXe,) or
 (eg1. Delphi7, Python, Java)  or (eg2. delphi7, C# ,VC#dot, VC+)
because many problems have original from external .dll (Vc2022) not from
Lazarus.
otherwise, You buy older computer and you can forced running Win8Lazarus8(x64)
or you combine Win8Lazarus(x64)  and LinuxLazarus(x32).
 

[cdbc]

Hi
@d2010: I'm sorry, but that's just useless driwel!!!
/b

[Thaddy]

Tested two win 11 installs (with jcl added, I normally don't use that)
-1 Intel64 2/4 core @2400 4 GB mem 1 TB spindisk: Lazarus starts in less than ~35 seconds ( very old laptop )
-2 Ryzen 8/16 core @4300 8 GB mem 500 GB ssd: Lazarus starts in less than ~2 seconds ( more recent, but average laptop )

Observe that the resource starved - minimum win11 hardware requirements  - and 6 year old laptop is indeed slow, but still acceptable.
My anti-virus is simply the OS provided Windows Defender. (Anything else makes no sense for home use, remove all others)

[af0815]

My anti-virus is simply the OS provided Windows Defender. (Anything else makes no sense for home use, remove all others)

My experience, some AVs are slow down everithing at startup. Some AV scanner send online samples of the Lazarus and fpc and you have wait minutes ! 

[Mr.Madguy]

What I've noticed - is that various tooltips are slow to load. For example one, that can be enabled/disabled via Environment->Object inspector->Info panel. But it's not only thing, that can cause IDE hanging. There is something else. I don't remember, what.

Don't get me wrong - my IDE starts almost instantly (~1s). But once I perform certain operations, IDE can become irresponsive for ~5 seconds. This includes clicking on anything in object inspector, when info panel is active, or trying to make new event handler via double clicking any event. This behavior appeared in one of the latest Lazarus versions. Something related to loading big tooltip DB or initial code analysis, that are performed without multithreading. May be connected to your problem.

[Martin_fr]

What I've noticed - is that various tooltips are slow to load. For example one, that can be enabled/disabled via Environment->Object inspector->Info panel. But it's not only thing, that can cause IDE hanging. There is something else. I don't remember, what.

Don't get me wrong - my IDE starts almost instantly (~1s). But once I perform certain operations, IDE can become irresponsive for ~5 seconds. This includes clicking on anything in object inspector, when info panel is active, or trying to make new event handler via double clicking any event. This behavior appeared in one of the latest Lazarus versions. Something related to loading big tooltip DB or initial code analysis, that are performed without multithreading. May be connected to your problem.

Probably completely different to the OT. But, if it happens, are there any error msgs shown in the "messages" window? (E.g. codetool error, parsing source. ...).
If so, and if your IDE is build with -gl then some of those print a stacktrace to the log (even if there is no log), and that can be very slow (5 to 10 secs each trace).

This (the trace print) can also happen, even if no error is shown in the messages window. You can run with --debug-log=c:\path\log.txt and search that.
Or better you can compile the IDE with -WC (tools > configure build ide), and then get a console window for the IDE in which you can see those infos immediately.