Bug 576418 - When source gets rebuilt, the UI freezes
Summary: When source gets rebuilt, the UI freezes
Status: CLOSED DUPLICATE of bug 450663
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.21   Edit
Hardware: PC Linux
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2021-10-04 03:34 EDT by Jens Reimann CLA
Modified: 2022-04-07 08:26 EDT (History)
1 user (show)

See Also:


Attachments
Installation details (1.00 MB, text/plain)
2021-10-04 03:35 EDT, Jens Reimann CLA
no flags Details
Freeze #1 (563 bytes, text/x-log)
2021-10-04 03:52 EDT, Jens Reimann CLA
no flags Details
Freeze #2 (563 bytes, text/x-log)
2021-10-04 03:52 EDT, Jens Reimann CLA
no flags Details
Freeze #3 (654.44 KB, text/x-log)
2021-10-04 03:53 EDT, Jens Reimann CLA
no flags Details
Freeze #4 (563 bytes, text/x-log)
2021-10-04 03:53 EDT, Jens Reimann CLA
no flags Details
Freeze logs (654.44 KB, text/x-log)
2021-10-04 03:59 EDT, Jens Reimann CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Reimann CLA 2021-10-04 03:34:21 EDT
When a projects gets automatically re-built, the whole UI freezes for this time.

The Eclipse IDE used for run compilations in the background, so you could see the task "Building …" in the status bar section and still use the IDE.

What happens now is that when I see "Building" (for a PDE based Java project), then the whole UI is frozen for this time. Only when the build is complete, it becomes usable again.

I think this is a major degradation of the whole experience, as literally every time you type something, you get mini freezes of the UI. And every time so change something that has a bigger impact, it gets worse.

Not only does this ruin the whole experience, to some degree it makes the IDE unusable.

As I haven't used the Eclipse IDE for a while, I am not sure when this behavior was introduced. Might have been in the last 18 months.
Comment 1 Jens Reimann CLA 2021-10-04 03:35:42 EDT
Created attachment 287249 [details]
Installation details
Comment 2 Andrey Loskutov CLA 2021-10-04 03:41:08 EDT
If you have UI Freeze Monitoring enabled, you should also see "freeze" errors reported to the error log view. If not, please create jstack thread dump at the moment where UI freezes.
Please attach either jstack dump or freeze reports.
Comment 3 Jens Reimann CLA 2021-10-04 03:52:27 EDT
Created attachment 287250 [details]
Freeze #1
Comment 4 Jens Reimann CLA 2021-10-04 03:52:43 EDT
Created attachment 287251 [details]
Freeze #2
Comment 5 Jens Reimann CLA 2021-10-04 03:53:03 EDT
Created attachment 287252 [details]
Freeze #3
Comment 6 Jens Reimann CLA 2021-10-04 03:53:19 EDT
Created attachment 287253 [details]
Freeze #4
Comment 7 Jens Reimann CLA 2021-10-04 03:59:05 EDT
Looks like Freeze monitoring is enabled by default. And it looks like "exporting logs" does something different than "exporting entries". Luckily I exported the log accidentally with "freeze #3", so that should contain the stack traces.
Comment 8 Jens Reimann CLA 2021-10-04 03:59:42 EDT
Created attachment 287254 [details]
Freeze logs
Comment 9 Andrey Loskutov CLA 2022-04-07 08:26:14 EDT
(In reply to Jens Reimann from comment #8)
> Created attachment 287254 [details]
> Freeze logs

Thanks. Finally got time to look into, and that is a duplicate of bug 450663 that is meanwhile fixed.

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