Bug 14769 - Xamarin Studio is going to be busy with opening c# code editor
Summary: Xamarin Studio is going to be busy with opening c# code editor
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.1.11
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
URL:
: 14797 ()
Depends on:
Blocks:
 
Reported: 2013-09-15 20:27 UTC by tome
Modified: 2013-09-23 04:02 UTC (History)
4 users (show)

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


Attachments
IDE log file (8.90 KB, text/plain)
2013-09-15 20:27 UTC, tome
Details
a sample of the process of Xamarin Studio in busy with Activity Monitor (275.41 KB, text/plain)
2013-09-17 01:40 UTC, tome
Details


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 FIXED

Description tome 2013-09-15 20:27:12 UTC
Created attachment 4892 [details]
IDE log file

Description of Problem:
Xamarin Studio is going to be busy, after once you open any C# code with editor.
It can be see 100% of CPU usage in the Activity Monitor.app.
(also I can feel my Mac Book hot with my palm)

It seems like it runs a busy loop in background thread. (Main UI thread is not stalled)
And found the error message "Failed to upload report to the server" in the log repeatedly.

Please let me know if you have a switch or something to stop this uploading behavior or any infos.

Steps to reproduce the problem:
1. Load any C# project then just open any C# code with editor

I tried with the other ex. C++ code, this is not going to busy.


Additional Information:

snippet from log;
ERROR [2013-09-16 08:07:44Z]: Failed to upload report to the server
System.Net.WebException: The request timed out
  at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00065] in /private/tmp/source/bockbuild-xamarin/profiles/mono-mac-xamarin-no-pcl/build-root/mono-3.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:951 
  at System.Net.HttpWebRequest.GetResponse () [0x0000e] in /private/tmp/source/bockbuild-xamarin/profiles/mono-mac-xamarin-no-pcl/build-root/mono-3.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:957 
  at MonoDevelop.Core.LogReporting.LogReportingService.TryUploadReport (System.String filename, System.Byte[] data) [0x00102] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-4.1.11-branch/6df7ab66/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.LogReporting/LogReportingService.cs:180 
ERROR [2013-09-16 08:09:25Z]: Failed to upload report to the server
System.Net.WebException: The request timed out
  at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00065] in /private/tmp/source/bockbuild-xamarin/profiles/mono-mac-xamarin-no-pcl/build-root/mono-3.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:951 
  at System.Net.HttpWebRequest.GetResponse () [0x0000e] in /private/tmp/source/bockbuild-xamarin/profiles/mono-mac-xamarin-no-pcl/build-root/mono-3.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:957 
  at MonoDevelop.Core.LogReporting.LogReportingService.TryUploadReport (System.String filename, System.Byte[] data) [0x00102] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-4.1.11-branch/6df7ab66/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.LogReporting/LogReportingService.cs:180 
...


Thank you for your help.
Comment 1 Thomas Peterson 2013-09-15 21:20:12 UTC
I have the same Problem after loading an c# file cpu goes to 100%.
Comment 2 Thomas Peterson 2013-09-16 11:33:11 UTC
Sorry thats an big Problem i can not work. MonoDevelop has no issues
Comment 3 tome 2013-09-16 14:56:51 UTC
Indeed, this importance should be raised more serious.
FYI. i found the failed http request is to;

http://monodevlog.xamarin.com:35162/logagentreport


And i confirmed that could not reach to there with traceroute in reasonable duration.
% nslookup monodevlog.xamarin.com
Non-authoritative answer:
monodevlog.xamarin.com	canonical name = ec2-50-16-131-78.compute-1.amazonaws.com.
Name:	ec2-50-16-131-78.compute-1.amazonaws.com
Address: 50.16.131.78

% traceroute monodevlog.xamarin.com
<snip>
13  ae-5.amazon.asbnva02.us.bb.gin.ntt.net (168.143.232.74)  177.107 ms
    ae-2.amazon.asbnva02.us.bb.gin.ntt.net (168.143.228.38)  154.499 ms  162.330 ms
14  72.21.220.25 (72.21.220.25)  174.498 ms  172.487 ms
    72.21.220.33 (72.21.220.33)  182.407 ms
15  72.21.222.141 (72.21.222.141)  175.727 ms  170.555 ms  176.820 ms
16  * * *
...


Thank you for your help.
Comment 4 Alan McGovern 2013-09-16 15:29:49 UTC
Those warnings can be safely ignored. They are not a cause/symptom of the issue. Can you do a quick test for me:

1) Launch Xamarin Studio - see if the CPU usage is normal/too high
2) Create a new C# Console application - see if CPU usage is normal/high
     - If the CPU usage is high, wait a few minutes and see if it goes back to normal
3) Create a new MonoTouch (storyboard) application - see if the CPU usage is normal/high

Can you also then give us all the information in the 'Xamarin Studio -> About Xamarin Studio'  window. If you click on 'Show details' there'll be a button to copy all the info to your clipboard so you can send it to us.
Comment 5 Thomas Peterson 2013-09-16 21:26:53 UTC
Ok The cpu begins when i open the text editor.
And only in the alpha version.
in 4.0.12 no problems.

=== Xamarin Studio ===

Version 4.1.11 (build 10)
Installation UUID: 5dce0ecf-db51-427d-805b-7b21e36f40e2
Runtime:
	Mono 3.2.2 ((no/a0fc6ba)
	GTK+ 2.24.20 theme: Raleigh
	GTK# (2.12.0.0)
	Package version: 302020000

=== Apple Developer Tools ===

Xcode 4.6.3 (2068)
Build 4H1503

=== Xamarin.iOS ===

Version: 6.4.5.0 (Trial Edition)
Hash: 1336a36
Branch: 
Build date: 2013-10-09 11:14:45-0400

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.Android ===

Version: 4.8.2 (Starter Edition)
Android SDK: /Users/boonkerz/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0   (API level 14)
		4.0.3 (API level 15)
Java SDK: /usr
java version "1.6.0_51"
Java(TM) SE Runtime Environment (build 1.6.0_51-b11-457-11M4509)
Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-457, mixed mode)

=== Build Information ===

Release ID: 401110010
Git revision: 6df7ab667918ee55a75f1adc93d53e3c9db392ae
Build date: 2013-09-14 00:09:49+0000
Xamarin addins: 7b3a1cd0b47c2a7b4530aaa2cc5e0077ee1001db

=== Operating System ===

Mac OS X 10.8.4
Darwin boon.local 12.4.0 Darwin Kernel Version 12.4.0
    Wed May  1 17:57:12 PDT 2013
    root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64
Comment 6 tome 2013-09-17 01:34:39 UTC
Thomas-san said so and i also wrote; the trigger is the opening (any) C# code with editor.
Anyway, (sorry i am poor at English)

1. Launch Xamarin Studio
    CPU normal
2. Create a new C# Console application (and editor opened automatically)
    CPU high and keep on running at least 10 minutes (until quit Xamarin Studio)
3. (after Re-launch Xamarin Studio) Create a new MonoTouch application
    (and editor opened automatically)
    CPU high and keep on running (until quit Xamarin Studio)

No difference between 2 and 3.


=== Xamarin Studio ===

Version 4.1.11 (build 10)
Installation UUID: 25df58b1-f4e5-4930-a213-fb0769517c0e
Runtime:
	Mono 3.2.2 ((no/a0fc6ba)
	GTK+ 2.24.20 theme: Raleigh
	GTK# (2.12.0.0)
	Package version: 302020000

=== Xamarin.Android ===

Not Installed

=== Apple Developer Tools ===

Xcode 5.0 (3332.22)
Build 5A1412

=== Xamarin.iOS ===

Version: 6.9.7.13 (Business Edition)
Hash: e7c3c68
Branch: 
Build date: 2013-11-09 22:23:45-0400

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Build Information ===

Release ID: 401110010
Git revision: 6df7ab667918ee55a75f1adc93d53e3c9db392ae
Build date: 2013-09-14 00:09:49+0000
Xamarin addins: 7b3a1cd0b47c2a7b4530aaa2cc5e0077ee1001db

=== Operating System ===

Mac OS X 10.8.5
Darwin macaroon.local 12.5.0 Darwin Kernel Version 12.5.0
    Mon Jul 29 16:33:49 PDT 2013
    root:xnu-2050.48.11~1/RELEASE_X86_64 x86_64
Comment 7 tome 2013-09-17 01:40:24 UTC
Created attachment 4908 [details]
a sample of the process of Xamarin Studio in busy with Activity Monitor

FYI. There are 22 threads in the process
Comment 9 Alan McGovern 2013-09-17 12:43:49 UTC
*** Bug 14797 has been marked as a duplicate of this bug. ***
Comment 10 Alan McGovern 2013-09-17 12:46:42 UTC
The same issue has been reported on Windows and Mac.
Comment 11 Alan McGovern 2013-09-17 14:09:02 UTC
This issue seems to be fixed in newer 4.1.11 builds. I don't know what caused it but issuing a new 4.1.11 release should resolve it for everyone else too.
Comment 12 Thomas Peterson 2013-09-17 14:32:14 UTC
ok how can we update :)
Comment 13 Thomas Peterson 2013-09-18 08:47:33 UTC
My Trial Periode runs out and i can not test it.
Comment 14 Alan McGovern 2013-09-18 09:02:53 UTC
There are two options currently:

1) Use Xamarin Studio Stable or Beta.
2) Wait for a new Xamarin Studio Alpha release.

We should be releasing a new alpha within the next couple of days. You could also try the previous alpha release as that should also be unaffected by this bug: http://download.xamarin.com/studio/Mac/XamarinStudio-4.1.10-14.dmg
Comment 15 Thomas Peterson 2013-09-18 09:04:38 UTC
The Stable has not the Storyboard Editor in the App itself thats an main Feature why i use the alpha currently :)

The previous i will test.

Thanks
Comment 16 Thomas Peterson 2013-09-18 09:09:48 UTC
ok this version helps a lot works under the mac very well :)

tome should also test
Comment 17 Alan McGovern 2013-09-18 09:11:41 UTC
The only thing to bear in mind is that iOS7 is not as well supported as iOS 6/iOS 6.1. I'd recommend using Xcode 4.6.x and iOS 6.x for your testing while we wait for iOS7 to be officially released and can release our official support for it.

If you're testing iOS7 in the mean time you may see some minor rendering issues.
Comment 18 tome 2013-09-18 14:11:29 UTC
Now I've tested. The 4.1.10 (build14) works fine for me too.
And I checked the 4.1.11 that is already available in the Alpha channel,
But the 4.1.11 does not include a fix of this issue.

Anyway, i can continue to work migration of my apps into iOS7 somehow.
Thank you for your help.
Comment 19 tome 2013-09-18 14:14:58 UTC
Sorry, I misunderstood that the 4.1.11 in the alpha channel means reverting version, not a new version.
Comment 20 Alan McGovern 2013-09-18 14:19:17 UTC
Yeah, you will have to wait for 4.1.12 or higher for a fix
Comment 21 Rogier Hofboer 2013-09-19 03:29:21 UTC
>And I checked the 4.1.11 that is already available in the Alpha channel
The the latest version my Xamarin Studio finds in the Alpha channel is 4.1.10.

Version 4.1.10 also has the issue

In fact all available versions have the issue,
but the strange thing is it does not happen on all machines?!?!

On my desktop the issue is not present (Windows 7 x64)
but on my company laptop the issue is present (also Windows 7 x64)
Comment 22 Alan McGovern 2013-09-19 09:50:42 UTC
I'm reopening this until we can be 100% sure we've released a version which fixes this problem. Some people are still experiencing this with our latest builds internally so it must not be fixed as I originally thought.
Comment 23 Mike Krüger 2013-09-23 04:02:49 UTC
should be fixed