Bug 3129 - hang and high cpu usage when deploying
Summary: hang and high cpu usage when deploying
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: 2.8.6
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: shana@xamarin.com
URL:
Depends on:
Blocks:
 
Reported: 2012-01-28 16:05 UTC by Chris Toshok
Modified: 2013-12-05 18:34 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Chris Toshok 2012-01-28 16:05:42 UTC
version 2.8.6.2, actually.

tried deploying app to the simulator, it finished uploading it but the install never happened.  after 30 minutes of nothing happening, I quit the simulator.  now monodevelop is saying:

- waiting for device -

in the Deploy to Device pad, and is using 31% cpu:


30776- mono         31.1 39:22.28 1/1   0    9     1263  551M   92M    880K   656M   1411M  17534 1     running  501  737845616+ 119      737845351+  179897+    1029       16         25710941+  1
0      kernel_task  30.4 03:05:11 85/9  0    2     1398  53M    0B     764M+  58M    7192M  0     0     running  0    25208      0        1783525462+ 997476852+ 0          0          476067736+

kill -QUIT shows the following in the log file:


Full thread dump:

"<unnamed thread>" tid=0x0xb050d000 this=0x0x4c6bd0 thread handle 0x40d state : interrupted state owns ()
  at (wrapper managed-to-native) System.Threading.Thread.Sleep_internal (int) <0xffffffff>
  at System.Threading.Thread.Sleep (int) <0x00017>
  at MonoDevelop.Projects.Formats.MSBuild.MainClass/<WatchProcess>c__AnonStorey0.<>m__0 () <0x0001f>
  at System.Threading.Thread.StartInternal () <0x00059>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

"<unnamed thread>" tid=0x0xac52b2c0 this=0x0x4c6f18 thread handle 0x403 state : waiting on 0x400 : Event  owns ()
  at (wrapper managed-to-native) System.Threading.WaitHandle.WaitAny_internal (System.Threading.WaitHandle[],int,bool) <0xffffffff>
  at System.Threading.WaitHandle.WaitAny (System.Threading.WaitHandle[]) <0x00027>
  at MonoDevelop.Projects.Formats.MSBuild.MainClass.Main (string[]) <0x0017b>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff>

"<unnamed thread>" tid=0x0xb0307000 this=0x0x3c13690 thread handle 0x415 state : interrupted state owns ()
  at (wrapper managed-to-native) System.Threading.Thread.Sleep_internal (int) <0xffffffff>
  at System.Threading.Thread.Sleep (int) <0x00017>
  at System.Runtime.Remoting.Channels.Tcp.TcpConnectionPool.ConnectionCollector () <0x00037>
  at System.Threading.Thread.StartInternal () <0x00059>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

"<unnamed thread>" tid=0x0xb040b000 this=0x0x4c6540 thread handle 0x40b state : interrupted state owns ()
  at (wrapper managed-to-native) System.Net.Sockets.Socket.Accept_internal (intptr,int&,bool) <0xffffffff>
  at System.Net.Sockets.Socket.Accept () <0x0007f>
  at System.Net.Sockets.TcpListener.AcceptSocket () <0x00023>
  at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.WaitForConnections () <0x0003b>
  at System.Threading.Thread.StartInternal () <0x00059>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>
Comment 1 Mikayla Hutchinson [MSFT] 2012-01-30 12:26:46 UTC
That appears to be a dump of the MSBuild remote process, which is idle. Are you sure you did the kill -QUIT on the correct process?
Comment 2 PJ 2013-11-19 17:04:41 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:34:50 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.