Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
System.NullReferenceException in CombinableComponentUpdateData (diagnostic output)
Options
Previous Topic Next Topic
GreenMoose
#1 Posted : Thursday, November 21, 2013 5:52:20 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 507

Thanks: 145 times
Was thanked: 66 time(s) in 64 post(s)
v1.48.0.5 / vstudio 2012 premium

I keep getting tons of exceptions like below in diagnostic output (summary level)
Quote:

[06:48:56.782-Core-97] ERROR (Internal): System.NullReferenceException: Object reference not set to an instance of an object.
at nCrunch.Client.Model.EngineWorkflow.(CombinableComponentUpdateData )
at nCrunch.Client.Model.EngineWorkflow..()
at nCrunch.Common.QueuedActionHandler.#=qLLN_sbMf6B6Fj0_gLEYQIw==(#=qmKU5DO9Zs_4a1ZzeI2XJP5ykxyw4hFpUU3fEvqo2Rqg= #=qGO84mtW4HzZQwLwHhN3fXQ==)



I've tried removing _Ncrunch subfolder and rerunning all tests, still same exception.

Is there something I do anything about it (except simply disabling diagnostic output) or is is it better to downgrade?

Thanks.
Back to top
Remco
#2 Posted : Thursday, November 21, 2013 8:29:44 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,123

Thanks: 957 times
Was thanked: 1286 time(s) in 1193 post(s)
Hi -

Thanks for sending through the bug report for this one. Is there anything specific that seems to have triggered it? Does changing the sliding build delay to either a non-zero or zero value (opposite to what you have at the moment) make any difference? Have you noticed anything else wrong in the engine other than the exception being reported?
Back to top
GreenMoose
#3 Posted : Thursday, November 21, 2013 10:27:22 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 507

Thanks: 145 times
Was thanked: 66 time(s) in 64 post(s)
Remco;4824 wrote:
Is there anything specific that seems to have triggered it?

Not from I can tell. It all started after upgrade (granted, it's been some weeks since I used diagnostic output).
However it does flood the output constantly, even when NCrunch engine is idle.

Remco;4824 wrote:
Does changing the sliding build delay to either a non-zero or zero value (opposite to what you have at the moment) make any difference?

If I change, and close/reopen solution, yes. 0 will remove them all together. 5000 they appear every 5s. With 50 they will flood diagnostic output.

Remco;4824 wrote:
Have you noticed anything else wrong in the engine other than the exception being reported?

No, if disabling diagnostic output it seems fine (even with sliding build delay of 50).
Back to top
Remco
#4 Posted : Thursday, November 21, 2013 10:46:00 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,123

Thanks: 957 times
Was thanked: 1286 time(s) in 1193 post(s)
My theory is that this is a wayward timer that isn't stopping when it should be. The exceptions shouldn't cause any problems other than just general noise in the output. Provided the sliding build delay isn't set too low, you shouldn't notice any loss in performance.

I'll investigate this to see if I can sort it out. Thanks for reporting it.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.031 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download