This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 158314 - Search History query runs on UI thread
Summary: Search History query runs on UI thread
Status: VERIFIED DUPLICATE of bug 152351
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Subversion (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-10 14:45 UTC by mjreged
Modified: 2009-04-28 11:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mjreged 2009-02-10 14:45:45 UTC
Every time i perform search on one of my subversion tree the entire netbeans IDE UI freezes until some results come 
back. For a long running query this is very frustrating and unprofessional. Please put the long running process in 
SwingWorker Thread and provide status update.
Comment 1 Tomas Stupka 2009-02-10 15:06:05 UTC
unfortunately, i can't reproduce. we would need more info from you:

- what build do you use?
- any chance to provide a thread dump while the IDE is hanging? - see http://wiki.netbeans.org/GenerateThreadDump
- your messages.log could be also of use

thanks

Comment 2 mjreged 2009-02-21 14:30:23 UTC
What do you mean you can't reproduce, every person at work that i recommended installing netbeans6.5 that checked out a
subversion tree then opened search history and clicked the button search told me about this behavior. It's stable
version of netbeans man. There is no errors. Don't be ignorant. If i download the netbeans code and navigate to this
plugin and find the button and i see that the action runs on swing thread i will make a big stink about you wasting my time.
Comment 3 Ondrej Vrabec 2009-02-21 16:57:28 UTC
Hi,
we could not reproduce without knowing your build version. I think this problem was fixed about 2 month ago in #152351.

BTW, we are not ignorant, we just need enough information to identify your problem and find out if it has not already
been fixed, which we did once you provided us with the build number you were using.

*** This issue has been marked as a duplicate of 152351 ***
Comment 4 Petr Dvorak 2009-04-28 11:43:13 UTC
Verified - duplicate.