Community
Participate
Working Groups
Starting with Eclipse SDK RC1, unzipped, I then unzipped other WTP pre-reqs into 'eclipse' directory (such as EMF and GEF, was the smallest set I tested, but started testing with several larger sets :( ). Then when I selected "software updates" the IDE "hung" ... such as being infinitly busy (busy cursor was 'on', when I clicked on task bar to close got the windows "not responding" message) and eventually I had to kill it. (I just let it run a minute or so, not sure if infinite loop, or just a very very long iteration). When I did same test, starting fresh of course, unzipping those 2 pre-reqs into 'dropins' directory then everything worked as expected and the software updates dialog came up within a second or two. I think this would be "blocking" for release of 3.4, but is not preventing me from testing, since I can work around by getting set-up using 'dropins', so marked as major.
Well ... I'm not sure what I'm seeing here. I sometimes do see very long delays in 'dropins' after all, and when I just tried to catch a thread dump in the 'eclipse' case, it finished just about the time the thread dump did ... so, maybe there's not a bug here, per se, just very variable times to bring up the 'software updates' dialog?
Yes, this is unrelated to dropins, although the dropins content could influence what repos we are trying to load. This is a performance regression introduced by the support for externalized string lookup on IU's. Once repos are cached, things speed up significantly, but the cache is a soft reference so you might see things working quickly and then the hang again. In RC2 we have made the dialog open faster, and we are making incremental improvements to the underlying performance issues. *** This bug has been marked as a duplicate of bug 232413 ***
