History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEA-15413
Type: Performance Problem Performance Problem
Status: Open Open
Assignee: Dmitry Jemerov
Reporter: Simon Knott
Votes: 2
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
IDEA: Feedback

"Discovering location for x" background task hogs CPU

Created: 03 Oct 07 15:13   Updated: 25 Oct 07 14:46
Component/s: Version Control Integration

File Attachments: 1. Zip Archive 7318_simonk_03.10.2007_12.08.11.zip (1.44 Mb)
2. Zip Archive 7346_simonk_12.10.2007_16.48.04.zip (1.99 Mb)

Environment: Windows XP, JDK6U2

Build: 7,318
Severity: High


 Description  « Hide
After a project start, the CPU appears to be maxed out for a few minutes while it runs the background tasks of "Discovering location for module_root".

CPU profile attached.



 All   Comments   Work Log   Change History      Sort Order:
Dmitry Jemerov - 03 Oct 07 15:36
How many changes are shown in the Incoming tab for you? Are they correct?

Simon Knott - 03 Oct 07 15:48
I've got 9 incoming changes apparently and they are all incorrect (see IDEA-13426 for previous reporting of this).

I was going to send you a log file with the results of the Incoming Changes refresh, but the button has just greyed itself out...


Simon Knott - 03 Oct 07 15:58
I should also add that due to an exception in the Committed Cache my Repository tab is completely empty and grey! I have no idea whether this is linked however. My Incoming Changes tab has been wrong forever.

2007-10-03 12:42:20,843 [2377099] ERROR - plication.impl.ApplicationImpl -
java.lang.AssertionError
at com.intellij.openapi.vcs.changes.committed.CommittedChangesCache.getChanges(CommittedChangesCache.java:235)
at com.intellij.openapi.vcs.changes.committed.CommittedChangesCache$2.run(CommittedChangesCache.java:9)
at com.intellij.openapi.progress.BackgroundTaskQueue$1.run(BackgroundTaskQueue.java:49)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$5.run(ProgressManagerImpl.java:2)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:1)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:67)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:52)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$6.run(ProgressManagerImpl.java:1)
at com.intellij.openapi.application.impl.ApplicationImpl$5.run(ApplicationImpl.java:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:4)


Dmitry Jemerov - 03 Oct 07 16:01
This assertion will be fixed in next RC.

Simon Knott - 03 Oct 07 16:03
Great - can I increase the logging on the Incoming Changes? I've got some very generic log statements, saying they've found new change lists, but it doesn't specify what's triggered the change list as "Incoming" currently.

Evan Leonard - 11 Oct 07 23:05
Probably not the same problem, but I hate when I see this... invariably IDEA hogs the cpu for while when this happens. Sometimes that message shows up in the middle of while I'm working and I have to wait half a minute to get back to work :-/ (same build 7318)

Dmitry Jemerov - 11 Oct 07 23:07
Evan,

Could you please capture a snapshot when this happens for you, so that we could check if it's the same problem or not?


Simon Knott - 12 Oct 07 20:06
I've attached another CPU snapshot in the hopes that this gets addressed.

This is the CPU profile for 15 minutes while it was stuck in the "Discovering location" background task. The CPU was virtually maxed out for the full 15 minutes and was stuck on one module's particular revision. Looking at the revision in Subversion, it has a 4K delta, so it's not even as though it's a large change.


Simon Knott - 25 Oct 07 14:46
Is there any update for this issue? Until this is resolved we can't upgrade our development team to IDEA 7, because it just kills the IDE.