Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [aeri] Skipping UI freeze reports caused by OSGI class loading for Mars.1?

This has been a problem for many years. I’m not sure much can be done.
Though there may be cases where whatever is triggering the plug-in loads
could be moved to a background job. To help understand that, the logs
would be interesting for those cases. How much of this is done by the
platform UI? How much by sloppy code or old code? How much is unavoidable.

It certainly annoys users and would be worth characterizing at least.


On 2015-08-25, 1:57 AM, "cross-project-issues-dev-bounces@xxxxxxxxxxx on
behalf of Marcel Bruch" <cross-project-issues-dev-bounces@xxxxxxxxxxx on
behalf of marcel.bruch@xxxxxxxxxxxxxx> wrote:

>Dear cross-projects,
>I’m currently investigating ui freeze reports.
>Many of those freezes are caused by loading classes or resources from zip
>files inside the UI thread.
>I tend to believe that those UI freezes cannot be „fixed“ by "loading
>classes in the background“ and also believe that these freezes are
>annoying for users as well.
>If anyone actually cares for those ui freezes or anyone has some great
>recommendations how to deal with those freezes, let me know.
>Otherwise I’ll stop collecting ui freezes that contain "at
>org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass“ and
>This change would go live in Mars.1.
>Discussions can take place in bug 475755 [3].
>Codetrails GmbH
>The knowledge transfer company
>Robert-Bosch-Str. 7, 64293 Darmstadt
>Phone: +49-6151-276-7092
>Mobile: +49-179-131-7721
>Managing Director: Dr. Marcel Bruch
>Handelsregister: Darmstadt HRB 91940
>cross-project-issues-dev mailing list
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit

Back to the top