Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Reporting interactive UI delays into the Error log

Hi Lars

Really good initiative.

But on a very new Windows 8.1 64 bit machine with minimal running applications, even the Error Log view triggers the 0.5 second threshold. The log fills at a rate of about 10 entries per minute. Many logged delays are in the 5 to 10 second range, suggesting that my Eclipse should be glutinous, but it feels fairly normal.

Is this tool ready for use yet?

The original Bugzilla has some discussion on a UI and preferences, but I can't see any preferences. Am I blind (again)?

Once a Bugzilla has been logged against some suspected offender, it would be nice to be able to filter further logs from that offender.


        Ed Willink

On 02/09/2014 11:09, Lars Vogel wrote:

Sometimes the Eclipse IDE freezes without providing feedback which part of the code is responsible for the freeze. Such freezes should be avoided, but it is often hard to determine the cause of the freeze.

Platform.ui received a code contribution in to report such UI delays into the Error View. In its default configuration it report delays >  500 ms and adds a stack trace of the currently running code to the log entry. 

You can try this feature out from the following update site:  Works in Luna and Mars.

Platform.ui is planning to add this feature (deactivated by default) to the Mars release. Feedback is welcome, if you find bugs in the tool, please reported them

Best regards, Lars

P.S. I have not yet tried it if the interactive error reporting from Marcel but as UI delays are also reported to the Error log, Marcels plug-in should also report it.

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

No virus found in this message.
Checked by AVG -
Version: 2014.0.4765 / Virus Database: 4015/8166 - Release Date: 09/06/14

Back to the top