Bug 573038 - Eclipse IDE take too long to start up and slow
Summary: Eclipse IDE take too long to start up and slow
Status: CLOSED DUPLICATE of bug 548443
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.20   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-21 07:51 EDT by Ishika Keshwani CLA
Modified: 2021-11-02 03:47 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ishika Keshwani CLA 2021-04-21 07:51:37 EDT
Even after having a pc with a decent configuration, the eclipse takes too long to start up and works a little slow. I am having a pc with an 8 Gb ram, a 2 GB latest graphics card, and an SSD inbuilt but whenever I start eclipse it takes a while to start up. I had also compared the starting up time with other IDE's similar to eclipse ( IntelliJ and android studio) and found it is not the case with these IDE's. Eclipse takes around 30 seconds to around a minute to start up. I have used eclipse in the past but back then I never faced or felt anything like this. It may be something with my pc or there is some problem. I have been looking online and found a lot of other people having an issue with the booting time and slow working of the eclipse. sometimes it just hangs for a second like a frame drop in a video and it feels a little disturbing and annoying. please have a look at the problem.
Comment 1 Lars Vogel CLA 2021-04-21 08:00:05 EDT
Which version do you use?
Comment 2 Thomas Wolf CLA 2021-04-21 08:32:42 EDT
Is a virus scanner interfering? Exclude Eclipse and %HOME%\.p2 from the virus scanner?

Is your workspace on a local disk? If you have projects imported from git repositories: are the git repositories and their working directories on a local disk?
Comment 3 Rolf Theunissen CLA 2021-04-21 09:41:22 EDT
There is a note to Windows 10 users on the New and Noteworthy page, though that issue affects any Java process (or for that matter any process accessing jar files):
https://www.eclipse.org/eclipse/news/4.19/

Which links to Bug 548443, see also here: https://github.com/microsoft/java-wdb/issues/9
Comment 4 Lars Vogel CLA 2021-10-28 08:30:18 EDT
Latest I-build also starts super slow for me. It even seems to hang sometimes since todays I-build. Jörg, do you see the same?
Comment 5 Andrey Loskutov CLA 2021-10-28 09:03:37 EDT
(In reply to Lars Vogel from comment #4)
> Latest I-build also starts super slow for me. It even seems to hang
> sometimes since todays I-build.

Please define "super slow". Compared to your expectations, it is 1 seconds slower, 10, 100 seconds or 10 times slower?

I'm running the latest nightly and don't see anything suspicious, but I've never measured startup times. If it is reproducible, please create some jstack dumps.
Comment 6 Jörg Kubitz CLA 2021-10-28 09:07:47 EDT
(In reply to Lars Vogel from comment #4)
> sometimes since todays I-build. Jörg, do you see the same?

tested I20211027: started 10 times in ~4 sec
thats normal.
Comment 7 Lars Vogel CLA 2021-10-29 06:20:04 EDT
(In reply to Andrey Loskutov from comment #5)
> (In reply to Lars Vogel from comment #4)
> > Latest I-build also starts super slow for me. It even seems to hang
> > sometimes since todays I-build.
> 
> Please define "super slow". Compared to your expectations, it is 1 seconds
> slower, 10, 100 seconds or 10 times slower?

~30 seconds instead of 4-8 seconds which I typically see on Windows. But looks like this only happens if I run a screensharing software (Goto Meeting), so my case is not a windows case.

@Ishika, do you still see this slow startup with latest I-build from https://download.eclipse.org/eclipse/downloads/?
Comment 8 Lars Vogel CLA 2021-11-02 03:47:49 EDT
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=548443#c28 for steps to exclude Eclipse from the virus check and please vote for https://github.com/microsoft/java-wdb/issues/9

*** This bug has been marked as a duplicate of bug 548443 ***