Bug 559756 - Performance regression
Summary: Performance regression
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.15   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-31 14:25 EST by elatllat CLA
Modified: 2024-01-23 02:25 EST (History)
0 users

See Also:

Attachments
CPU Sample image (338.80 KB, image/png)
2020-01-31 14:25 EST, elatllat CLA 		no flags Details
data (22.29 KB, application/octet-stream)
2020-01-31 14:34 EST, elatllat CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description elatllat CLA 2020-01-31 14:25:36 EST 
Created attachment 281671 [details]
CPU Sample image

After upgrading the whole UI is lagging even just switching Tabs.
CPU Sample image attached.
Comment 1 elatllat CLA 2020-01-31 14:34:18 EST 
Created attachment 281672 [details]
data
Comment 2 elatllat CLA 2020-02-11 12:31:02 EST 
Trying to copy paste is a good way to reproduce this.
The UI can lag with 0% CPU use for ~60 seconds.
We had to go back to using 2019-12 and netbeans.
Comment 3 Eclipse Genie CLA 2022-02-01 19:40:48 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2024-01-23 02:25:43 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.