Thanks, Wim. Observed with JDT core, if lots of log entries are written, the UI become unresponsive.
I don't have a "ready to go" test case but have observed this frequently over the last years. In most case the underlying reasons for these error messages have been fixed but it has not been investigated if using a cache or a buffer would help for these case. Created https://bugs.eclipse.org/bugs/show_bug.cgi?id=551246 On Thu, Sep 19, 2019 at 1:24 PM Wim Jongman <wim.jong...@gmail.com> wrote: > > > currently writing lots of entries to the error log can cause UI freezes. > > I think I want to take a look at that. Flushing the SWT event queue during > writing to our error log has helped our application get rid of those freezes. > > Do you happen to know the bug number? > > On Thu, Sep 12, 2019 at 5:44 PM Lars Vogel <lars.vo...@vogella.com> wrote: >> >> I know that statement would trigger a reply. :-) >> >> I think Dirk's vision is to deprecate all other logging approaches or >> fascade them. >> >> Would IMHO be nice to have one simple and fast way of logging. For example, >> currently writing lots of entries to the error log can cause UI freezes. >> >> Mickael Istria <mist...@redhat.com> schrieb am Do., 12. Sep. 2019, 17:40: >>> >>> >>> >>> On Thu, Sep 12, 2019 at 5:22 PM Lars Vogel <lars.vo...@vogella.com> wrote: >>>> >>>> Having one logging solution would be great, as you pointed out it must >>>> be simple for the IDE case and the e4 RCP case. >>> >>> >>> As mentioned in the previous thread, there are already N ways of logging, >>> so adding one more way won't make N+1 == 1. >>> All the logging approach that are already in are most likely meant to stay >>> as API, so before starting such refactoring, I think it needs to be >>> verified how much value is to be expected from it. >>> As spotted in the "only few committers care of know the details about >>> logging", I think that most contributors don't really care about logging >>> because while it might be not perfect, it just works fine in the current >>> state and changing this wouldn't provide much added value to them. >>> _______________________________________________ >>> platform-dev mailing list >>> platform-dev@eclipse.org >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://www.eclipse.org/mailman/listinfo/platform-dev >> >> _______________________________________________ >> platform-dev mailing list >> platform-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://www.eclipse.org/mailman/listinfo/platform-dev > > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev -- Eclipse Platform project co-lead CEO vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com _______________________________________________ platform-dev mailing list platform-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
