CODEWITHSUNDEEP
androideclipse
gadss
gadss

Reputation: 22509

the user operation is waiting for background work to complete

I am using eclipse junno for my IDE for developing android programs.

my problem is just like this one : User Operation is waiting for "Building Workspace"

why did it happened and how can I solve this? I have waited lots of time about this case.

right now it is look like this.

enter image description here

Upvotes: 33

Views: 60931

Answers (6)

Shadyar
Shadyar

Reputation: 845

If the issue is persist after restarting the machine, probebly you have a loop of dependencies in your modules. I.e. there is a dependency deadlock between your modules, eg. in PUM file of module1, it needs module2 and in PUM file of module2, it needs module1.
To solve the problem, verify your PUM files in your relevant modules or sub projects.

Upvotes: 0

Ram Chhabra
Ram Chhabra

Reputation: 441

try by creating a new workspace, it worked for me.

Upvotes: 0

Shivam Gupta
Shivam Gupta

Reputation: 1

For me the issue was with the build path of the maven project. Try configuring the build path and include only what is actually required is what i learnt. My parent maven project had 10+ child modules. My eclipse would take 3-4 mins waiting for background process for every file save. I removed [parent module]/src from the build path and restarted eclipse and issue got fixed.

Upvotes: 0

Lova Chittumuri
Lova Chittumuri

Reputation: 3323

Go to Project Menu Uncheck the Build automatically and Restart the Eclipse/STS IDE.

enter image description here

Upvotes: 3

vivek
vivek

Reputation: 1112

In my case, I increased values of -Xms and -Xmx args to 512 and 2048 respectively in eclipse.ini file. You can increase it according to you or according to your system ram.
And then restart eclipse.

Upvotes: 3

Tyler Treat
Tyler Treat

Reputation: 15008

Eclipse can have a tendency to hang sometimes for no apparent reason (usually because of memory). Just try restarting it and see if the problem persists. I've encountered this before and restarting Eclipse or the PC altogether usually solves it.

Upvotes: 25

Related Questions