This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 388736 - [Performance] Closing single/all editor(s) is very slow (Java, XML editors)
Summary: [Performance] Closing single/all editor(s) is very slow (Java, XML editors)
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.2.2   Edit
Assignee: Paul Webster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 385401 (view as bug list)
Depends on:
Blocks: 385272
  Show dependency tree
 
Reported: 2012-09-04 07:21 EDT by Piotr Findeisen CLA
Modified: 2013-01-17 12:58 EST (History)
9 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Findeisen CLA 2012-09-04 07:21:35 EDT
In Eclipse Juno i observer following operations very slow compared to Helios i used previously on the same machine:

 - closing single Java editor window
 - closing single XML editor window
 - closing all editor windows
 - closing other editor windows

'Very slow' means the GUI is not responsive for more than 2s even when single editor is closed. (Forgive me, but i don't know how to assess GUI performance correctly)

This does not happen at all times. Especially reopening the file and closing once again is usually smooth.

Eclipse runtime settings i tried
 - all defaults (in Helios all defaults worked fine)
 - increasing mem (-Xmn128m -Xms512m -Xmx2048m -XX:+UseParallelGC) -- this improved general responsiveness a bit
Comment 1 Piotr Findeisen CLA 2012-09-04 07:23:22 EDT
It *may* be because i have some view(s), like History view (CVS), that need update and that may involve network communication and such. If it is so, however, i would still consider it a bug -- such updates should be run async. Especially if they involve network communication.
Comment 2 Eric Moffatt CLA 2012-09-24 14:56:09 EDT
Piotr, have you by chance also switched to EGit ? It's known to have some areas (like refresh) that lock the UI periodically...
Comment 3 Piotr Findeisen CLA 2012-09-24 17:16:43 EDT
I've egit installed but i am not actively using it. When i observe 'sluggishness' all editors are open on files under CVS control.
Comment 4 Eric Moffatt CLA 2012-09-25 10:26:44 EDT
Could you attach a screenshot of your window when you are in this state ? This is the easiest way to capture the information about what types of editors you have... thanks.

There's an overall defect, bug 385272 that you may want to scan to see if you can see similarities between your structure and others.
Comment 5 Piotr Findeisen CLA 2012-09-25 12:01:02 EDT
Sorry, no screenshot now -- i will when i get back to work.

But this is always Java, XML editor or, sometimes HTML editor.

The bug 385272 -- i am watching it, but it is very generic issue. I mean exactly the operation i described in the summary, i.e closing editors.
(I very often do 'close others')
Comment 6 Paul Webster CLA 2012-12-13 15:41:52 EST
Many performance fixes have now been made in the Juno SR2 and Kepler development streams. Anyone still encountering problems is encouraged to move up to a recent milestone or stable build, or apply the official performance patch  on top of a Juno SR1 release package. Full details on the patch and background on the performance work can be found here:

http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation

If you continue to experience performance problems using Kepler M4 or later, Juno maintenance build M20121128-1200 or later, or using the Juno SR1 performance patch, please report a new bug with all the details.

PW
Comment 7 Szymon Ptaszkiewicz CLA 2012-12-19 06:24:28 EST
*** Bug 385401 has been marked as a duplicate of this bug. ***
Comment 8 Paul Webster CLA 2013-01-17 12:58:26 EST
In M20130116-1800

PW