Visual Studio freezes sometimes after a run

[idealist1508]

What for informations, can I provide, to diagnose what is going wrong?

[acken]

So Visual Sutdio is freezing entirely? When it happens what processes are
running in the background? Is the Testrunner still alive in the background?
You could also enable logging under configuration and send over the log
files generated to C:\Users\you\Appdata\local\mightymoose

-Svein Arne

On Fri, Nov 7, 2014 at 8:59 AM, idealist1508 [email protected]
wrote:

What for informations, can I provide, to diagnose what going wrong?

—
Reply to this email directly or view it on GitHub
#3.

Best regards
Svein Arne Ackenhausen

Blog - http://ackenpacken.blogspot.com/
Twitter - http://twitter.com/ackenpacken

[idealist1508]

So Visual Sutdio is freezing entirely?

Yes. Here is a list of processes and log files. It was the last run. I made "Build and Test All Projects" after VS was started.

Is the Testrunner still alive in the background?

How can I find it out?

[acken]

The test runner process is not there so it has completed. The
AutoTest.VM.exe is also running and seems to quit just fine when it no
longer can find VS. There was no AutoTest.Client.log?

-Svein Arne

On Mon, Nov 10, 2014 at 9:49 AM, idealist1508 [email protected]
wrote:

So Visual Sutdio is freezing entirely?

Yes. Here is a list of processes
https://gist.github.com/idealist1508/7ce98632ee2ee857df79 and log files
https://github.com/idealist1508/files/blob/master/Bugs/continuoustests/LogsVsFreezes.rar?raw=true.
It was the last run. I made "Build and Test All Projects" after VS was
started.

Is the Testrunner still alive in the background?

How can I find it out?

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

Best regards
Svein Arne Ackenhausen

Blog - http://ackenpacken.blogspot.com/
Twitter - http://twitter.com/ackenpacken

[idealist1508]

It was a complete folder ...Appdata\local\mightymoose

[idealist1508]

Is this correct settings for logging?

[idealist1508]

I made a video, maybe you can see what going wrong...
It seems to happen only on first run. If it works on first run then it works afterward.

[acken]

Just remembered that after enabling logging I think VS needs a restart for
the client log to appear. Do you have a link to the video that is not exe
compressed? Don't have a windows box around atm.

-Svein Arne

On Tue, Nov 11, 2014 at 9:07 AM, idealist1508 [email protected]
wrote:

I made a video
https://github.com/idealist1508/files/blob/master/Bugs/continuoustests/ct_freeze_debugger.exe?raw=true,
maybe you can see what going wrong...
It seems to happen only on first run. If it works on first run then it
works afterward.

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

Best regards
Svein Arne Ackenhausen

Blog - http://ackenpacken.blogspot.com/
Twitter - http://twitter.com/ackenpacken

[idealist1508]

I made avi, but it is 111 MB.

[idealist1508]

I know why AutoTest.Client.log was missing:
In a file MightyMoose\AutoTest.config was <Debugging>false</Debugging>. I changed it manually to true and AutoTest.Client.log was created. So here is AutoTest.Client.log

PS: There is also one another Autotest.config in MightyMoose\storage\Configuration\Ams_42eafca8aae89b65a7f7b1441dd8a457\ with <Debugging>true</Debugging>, but this value appears to be unrelevant. When I change settings in VS then this file is changed.

[acken]

Greg do you know what this might be?

On Wed, Nov 12, 2014 at 4:21 PM, idealist1508 [email protected]
wrote:

I know why AutoTest.Client.log was missing:
In a file MightyMoose\AutoTest.config was false. I
changed it manually to true and AutoTest.Client.log was created. So here
is an error message:

Updating margin for AutoTest.VS.RiskClassifier.Signature
Sending request for risk metric of System.Void Sagede.Officeline.Seos.Launcher.VmAgent.Program::Application_ThreadException(System.Object,System.Threading.ThreadExceptionEventArgs)
Risk: Message Found of AutoTest.VM.Messages.RiskMetricGeneratedMessage
Received risk metric from backend for System.Void Sagede.Officeline.Seos.Launcher.VmAgent.Program::Application_ThreadException(System.Object,System.Threading.ThreadExceptionEventArgs) count = 2
updating System.Void Sagede.Officeline.Seos.Launcher.VmAgent.Program::Application_ThreadException(System.Object,System.Threading.ThreadExceptionEventArgs) count =2 time = n. def. called count = 0

PS: There is also one another Autotest.config in
MightyMoose\storage\Configuration\Ams_42eafca8aae89b65a7f7b1441dd8a457
with true, but this value appears to be
unrelevant. When I change settings in VS then this file is changed.

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

Best regards
Svein Arne Ackenhausen

Blog - http://ackenpacken.blogspot.com/
Twitter - http://twitter.com/ackenpacken

[idealist1508]

I disable "risc margin" and profiler. VS is working now without problems.

[gregoryyoung]

Updating margin for AutoTest.VS.RiskClassifier.Signature
Sending request for risk metric of System.Void
Sagede.Officeline.Seos.Launcher.VmAgent.Program::Application_ThreadException(System.Object,System.Threading.ThreadExceptionEventArgs)
Risk: Message Found of AutoTest.VM.Messages.RiskMetricGeneratedMessage
Received risk metric from backend for System.Void
Sagede.Officeline.Seos.Launcher.VmAgent.Program::Application_ThreadException(System.Object,System.Threading.ThreadExceptionEventArgs)
count = 2
updating System.Void
Sagede.Officeline.Seos.Launcher.VmAgent.Program::Application_ThreadException(System.Object,System.Threading.ThreadExceptionEventArgs)
count =2 time = n. def. called count = 0

Hmm looks like getting arguments on a method failed. it shouldn't lock
in this case though (unless a thread exception is happening somewhere
else aside from this as it properly called back).

On Mon, Nov 17, 2014 at 10:44 AM, idealist1508 [email protected]
wrote:

I disable "risc margin" and profiler. VS is working now without problems.

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

Studying for the Turing test

[idealist1508]

So, what can i do?

[freeman42x]

Experiencing the same problem with the Visual Studio 2013 Community experimental extension.

After disabling "risc margin" and profiler as mentioned by @idealist1508 the IDE no longer hangs after automatically running the tests.

The issue can be reproduced for example by loading this project https://github.com/razvan-panda/Functional-Kats and causing an automatic test to run (with default extension configuration).

[wradecki]

Install 48 (for VS2013 integration), then 47 (another link) and it works :D

[gregoryyoung]

@svein any idea on what may be broken in the installer?

On Tuesday, February 10, 2015, Wiktor Radecki [email protected]
wrote:

Install 48 (for VS2013 integration), then 47 (another link) and it works :D

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

Studying for the Turing test

[acken]

That's interesting, Need to look at the commits between the version and see
what changed.

On Tue, Feb 10, 2015 at 10:03 PM, Greg Young [email protected]
wrote:

@svein any idea on what may be broken in the installer?

On Tuesday, February 10, 2015, Wiktor Radecki [email protected]
wrote:

Install 48 (for VS2013 integration), then 47 (another link) and it works
:D

—
Reply to this email directly or view it on GitHub
<
#3 (comment)
73779749>
.

Studying for the Turing test

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

Best regards
Svein Arne Ackenhausen

Blog - http://www.acken.no http://ackenpacken.blogspot.com/
Twitter - http://twitter.com/ackenpacken