Hmm.... what .NET version do you have installed?
sallz0r wrote:Hmm.... what .NET version do you have installed?
Looks like I have 2.0 SP2, 3.5 and 4 installed. I also have VS2k8 installed. From the crash report its using 4.0.
Hmm, this is driving me nuts! 🙂 Spent the last few hours looking at it, and am no closer. What OS are you using? (XP? 7? Vista?) I might try setting up a VM and seeing what happens on that...
Thanks,
Michael
sallz0r wrote:Hmm, this is driving me nuts! 🙂 Spent the last few hours looking at it, and am no closer. What OS are you using? (XP? 7? Vista?) I might try setting up a VM and seeing what happens on that...Thanks,
Michael
Grabbed a second identical laptop, this one never had any other .NET version than 4.0 and does not have VS installed and same issue.
Details are Win7 Home then upgraded to Win7 Pro. On the VM it was Win7 Pro from the start.
Can you post a Vixen Directory with everything configured so I can rule out the way I configure Vixen?
I can (and will in a tick), however it's almost definitely not a configuration issue. I'm suspecting it's a threading issue -- because the preview can be pretty UI intensive (all the elements are drawn by pixel-bashing using GDI), it's started off in it's own thread. There's lots of code there to try and be 'safe' with the threading, and it seems to work....... 99% of the time. It's those cases like you've outlined that it doesn't. 🙂
The annoying thing is that we can't reproduce it at all, and you seem to have it consistently failing, which leads me to think it's something related to the environment, OS, .NET, etc., etc..... just not sure what. I see you mentioned in a previous post that you have VS -- are you a developer at all? If so, I don't suppose there's any chance you could grab a copy of the source, and build/run it on your machine to see if it hangs/crashes the same way, and if so, we could track down exactly what's happening on your machine and why it's different. If not, that's no worries. 🙂
Just curious -- why do you have .NET 2.0 and 3.5 on a Win7 machine? I thought it came with .NET 4; did you manually install the others? ........ I might try that, and see if that affects anything.... (I've only got 4.0.30319 installed, apparently.)
Cheers,
Michael
sallz0r wrote:I can (and will in a tick), however it's almost definitely not a configuration issue. I'm suspecting it's a threading issue -- because the preview can be pretty UI intensive (all the elements are drawn by pixel-bashing using GDI), it's started off in it's own thread. There's lots of code there to try and be 'safe' with the threading, and it seems to work....... 99% of the time. It's those cases like you've outlined that it doesn't. 🙂The annoying thing is that we can't reproduce it at all, and you seem to have it consistently failing, which leads me to think it's something related to the environment, OS, .NET, etc., etc..... just not sure what. I see you mentioned in a previous post that you have VS -- are you a developer at all? If so, I don't suppose there's any chance you could grab a copy of the source, and build/run it on your machine to see if it hangs/crashes the same way, and if so, we could track down exactly what's happening on your machine and why it's different. If not, that's no worries. 🙂
Just curious -- why do you have .NET 2.0 and 3.5 on a Win7 machine? I thought it came with .NET 4; did you manually install the others? ........ I might try that, and see if that affects anything.... (I've only got 4.0.30319 installed, apparently.)
Cheers,
Michael
I can run it in VS from source and see if it provides any more information on the issue. I am a Program Manager for a software company, before you say it I was a developer but not in C# but have done a lot of Java so its not all that far off I would suspect. Yeah .NET 2/3.5 were installed for some legacy applications, that's why I wanted to test on an identical laptop without them ever installed.
Specs of the this machine are a i7-3610QM 2.3 Ghz (8 Core) with 8GB Ram, NVIDIA GTX 660M 2GB. I suspected at first it was an issue with multi-monitors (I have three attached) but rules that out already.
Send me a PM with the info to grab the source and I can at least try to provide a little bit more information.
Thanks for that. I just PM'd you with another version to try and see if we can get some useful logging out of it to determine what's happening. (I doubt it, but worth a try).
You can find the source for the whole thing here, on github: https://github.com/sall/vixen
No worries if you don't have a chance to go through it; if you do though, any info would be appreciated.
I'm about to crash -- super late here, this bug's been frustrating me and keeping me up! -- but will keep going when I get home from work tomorrow.
Cheers,
Michael
PS. just to confirm, it's only when you have the execution engine on, or turn it on, correct? ie. if the EE is on, the software hangs *as soon as* you add a preview module instance, correct? Do you even see the preview window come up at all, or does it hang before that? What happens to the windows when they hang -- do they keep updating/redrawing, or do they stop updating? (eg. if you drag another window across them, does it give artefacts? or do they redraw properly?)
Similarly, when you have the EE off, you can add the preview, configure it fine, etc., etc..... but then it's only when you START the EE with the preview enabled, correct?
Thanks for the info and your patience!
sallz0r wrote:Thanks for that. I just PM'd you with another version to try and see if we can get some useful logging out of it to determine what's happening. (I doubt it, but worth a try).You can find the source for the whole thing here, on github: https://github.com/sall/vixen
No worries if you don't have a chance to go through it; if you do though, any info would be appreciated.
I'm about to crash -- super late here, this bug's been frustrating me and keeping me up! -- but will keep going when I get home from work tomorrow.
Cheers,
MichaelPS. just to confirm, it's only when you have the execution engine on, or turn it on, correct? ie. if the EE is on, the software hangs *as soon as* you add a preview module instance, correct? Do you even see the preview window come up at all, or does it hang before that? What happens to the windows when they hang -- do they keep updating/redrawing, or do they stop updating? (eg. if you drag another window across them, does it give artefacts? or do they redraw properly?)
Similarly, when you have the EE off, you can add the preview, configure it fine, etc., etc..... but then it's only when you START the EE with the preview enabled, correct?
Thanks for the info and your patience!
You have a bit of it right, so I am just going to explain it all as to not cause confusion...
When EE is turned ON:
When I click Add New Preview a window pops up, I select Vixen Display Preview, then OK. No window pops up, the application goes gray and a windows dialog appears behind saying VixenApplication has stopped working. No exception dialog is displayed. In the Debug log file I find two lines that says Preview:Resize.
When EE is turned OFF:
I can add a new Preview, it shows up un-checked this time by default. Everything seems to be good, I can click OK and it saves. When I go back in and click Configure I get a dialog with the "System.NullReferenceException: Object reference not set to an instance of an object." Exception.
Here is the funny thing, Once I add it with the EE turned off, I can restart the application with EE running and see the preview window is there but not enabled, as soon as I click to enable it, I get a stopped responding dialog. Now the application lockup is not instant, it seems to be delayed 2~5 seconds after enabling the preview, but nothing happens during that time...
Yep, OK, perfect. That means it's roughly in line with what I'm thinking it could be (the general area), and with the output you sent me via PM.
Just to clarify -- the exception you get when trying to configure it with EE disabled is an unrelated issue, I believe. I haven't tested it myself, but I wouldn't be surprised if that's just because the preview setup is looking for some data that's not available when the EE is disabled.
With that debugging output you PM'd me I'll try a few different things tonight, and might make a few different versions to test to see if it helps at all. I'll get back to you later on. 🙂
Thanks again for the debugging help, and I'm sorry it's such an.... awkward process! Unfortunately in cases like this (when we can't reproduce it locally) it's sometimes the only option.
Cheers,
Michael
This probably has no bearing but am offering just in case. We also had application lockups that did not show until quad core machines started being used. We discovered all DotNet GUI updates are actually performed on a single thread. Consequently we had to ensure all GUI activity was marshaled to a single thread.
