Closed
Description
Describe the bug
Takes so much time to launch and load sketches that you allmostly forget what have you been waiting for, the load time is really too long in compare to the old IDE.
I have an M.2 and 2 x 4GB 3200 MHz RAM though it takes the 2.0 IDE around 31 Seconds to start and load a sketch while 4.5 Seconds at version 1.8.
To Reproduce
Steps to reproduce the behavior:
- Run a sketch
- Use a stop watch.
Expected behavior
I was expecting for much better launch time.
Desktop (please complete the following information):
- Windows 11
- 2.0.0-rc3
Activity
ubidefeo commentedon Mar 2, 2022
@zaid894
We are aware of the startup-time issue, but in order to better investigate can you give us more info?
libraries
folder)example:
Thank you :)
ckuethe commentedon Mar 3, 2022
In my current installation, I have 47 libraries (I used to have over 280) and 21 platforms. I just restarted the IDE and it took 19 seconds from typing
arduino-ide
in a terminal until my sketch was open.(Samsung Evo970+ SSD, 40GB Ram, "11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz")
Platforms:
Libraries
I see lots of stuff like this in the output: the IDE making a bunch of connections to check for updates before loading the editor. These checks should be deferred and run in the background.
ckuethe commentedon Mar 3, 2022
ubidefeo commentedon Mar 4, 2022
thank you @ckuethe for the comprehensive output.
we'll look into why all those signature errors show up
u.
ckuethe commentedon Mar 4, 2022
I don't think the signature errors are as important as not blocking app startup while checking for updates. When I turn off my network the IDE loads much more quickly:
root INFO Finished loading frontend application after 5.734 seconds
ckuethe commentedon Mar 14, 2022
Wow. rc5 is even worse.
input
generates incorrectboard_manager#additional_urls
entry in the CLI config #919kittaakos commentedon Mar 17, 2022
The IDE starts to
await
for theindex-update
in this commit: 9aff90b#diff-f463d1c276a9080ec522ead62c6dd596e5bf330b093b7d51b71738c9795d0fdaL60-R60.Auto index-update CLI changes:
core search
to update indexes only after 24h from last edit arduino-cli#1237 (👈 this could be interesting)I did some measurements on the
HEAD
(usingconsole.time
):No 3rd party URLs:
My 3rd party URLs:
rm -rf ~/Library/Arduino15/ && rm -rf ~/Documents/Arduino/libraries
):rm -rf ~/Library/Arduino15/ && rm -rf ~/Documents/Arduino/libraries
):(Note: the numbers do not necessarily add up, but
all >=
the sum of the sub-tasks.)On my dev env, zero cores and libs are installed. Still, the core index update takes a long time and heavily depends on the 3rd party URLs config.
stodge commentedon Mar 18, 2022
It can take 60s+ to load on my laptop, and seems to take at least 30s before there's any visual indication that it's loading. Admittedly I have an HDD and not an SSD, but something like Visual Code doesn't have this problem. I'm on Windows 10 - is there a way to show startup logs?
per1234 commentedon Mar 18, 2022
Hi @stodge. You should get everything of interest by starting the Arduino IDE from the command line.
I'll provide instructions for how you can do that and then share the output here:
(usually
C:\Program Files\Arduino IDE
orC:\Users\<user name>\AppData\Local\Programs\Arduino IDE
).PowerShell will now open with the current directory set to the Arduino IDE installation folder.
& ".\Arduino IDE"
.Debug output should now be printed to the PowerShell window as the Arduino IDE starts (or fails to start).
This will open a context menu.
This will select all the text in the PowerShell window.
This will copy the contents of the PowerShell window to the clipboard.
Please let me know if you have any questions or problems while following those instructions.
stodge commentedon Mar 18, 2022
Thanks. I ran the command as you suggested, and it did nothing for 5 minutes until I pressed RETURN in Power Shell. It still has the problem where you the splash logo sits over everything on the screen and you can't bring any other window on top of it. Will post the logs in a bit.
I started the IDE from the command line before you replied, but as a foreground process. Again, it didn't do anything for 5+{ minutes until I pressed return in PowerShell and both instances started at the same time.
I'll close both instances and restart. More later... Thanks.
18 remaining items