This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm running LightSpeed 5 with Visual Studio 2013 Ultimate (Update 4). When I edit LightSpeed data models in the designer, Visual Studio becomes unstable and frequently crashes. The most recent crash occurred after saving the *.lsmodel. The Windows Application Logs in Event Viewer has the following errors:
What would be causing this? How can these error be prevented? Many thanks. |
|
|
|
|
Hi, We get similar crashes in Visual Studio Premium 2013 Update 4 (and have been getting them for months). I was about to submit this issue - so can provide further example crash logs if needed. Cheers, Simon. |
|
|
|
|
Thanks, any additional logs would certainly be useful for investigating this.
|
|
|
|
|
Hello again, All that I have is attached (not sure why my event logs don't look as informative as the initial post). This is with nightly build LightSpeed50Professional-20140729 It seems to be timing related. I can get a crash every time by accessing the design surface, then clicking to other classes (usually takes a few back and forward clicks between other classes and the design surface). If you wait a few seconds before clicking away from the design surface the crash doesn't usually occur. I've been doing my design surface work separately from my other development - to detour the crash. We use Resharper 8 C# Edition, if that makes any difference. Cheers, Simon. |
|
|
|
|
I've also found this entry in the Windows Application log at the same time as the errors:
The crash log in C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrashdevenv.exe8be03468606e212652d52dd2fbc8a338846a372ee1d7610664474351 (Report.wer) is attached. The WER1E06.tmp.WERInternalMetadata.xml file in the first path seems to have been deleted. Help -> About Microsoft Visual Studio produces the following (using the Copy Info button):
Hope this helps. Are there other additional logs you know of that would also help? Many thanks, Daniel |
|
|
|
|
Well at least you get it to crash. I cant seem to get it to install and let me add a design surface. It installs with visual studio 2013 checked but theres no model to add in the items. |
|
|
|
|
Hi there. I am getting the same issue with the regular crashing of VS2013 Update 4 (although it was happening on earlier updates and VS2012 too) as well. Have been for months. It'd be great to get a fix for this. Sometimes it doesn't crash but more often than not. |
|
|
|
|
I have decided to leave the lightspeed reservation. The support, if this meager forum is it, is not cutting it. I have gone back to Entity Framework, and rolling my own repository and Unit of work layers. Lots of information out there and I have to say that Entity Frameworks is mature and well behaved and I like the fact that there is information and articles and examples littered over the internet. While is was very impressed with Lightspeed at first because Entity Framework seemed as is sometimes typical of certain MS technologies, over-thought and over-wrought-but it really pretty darn nice. It an example of the value of information over brilliant but spotty software. Lucky i purchased my copy during a rare cyber monday deal and i'm only resentful for 200 dollars. It interesting that lightspeed and EF do about the same thing only lightspeed just seems to have odd issues that slow you down. |
|
|
|
|
I've had another crash, which occurred when Saving All after editing the LightSpeed designer file. 1st log entry:
2nd log entry:
3rd log entry:
4th, 5th and 6th log entry:
What is happening in terms of fixing this issue? |
|
|
|
|
What version are you running? Can you try updating to the latest nightly build as we have included some recent updates which we are hoping will address this.
|
|
|
|
|
Can anyone who has upgraded to the latest nightly build post back with their experience ? We would like to know that the fault has been fixed before upgrading - if possible. Cheers, Simon. |
|
|
|
|
I got another crash this morning - the first since I upgraded to the nightly build 20150305 (which was the latest at the time of Jeremy's reply). Here's a collection of messages from my Windows Application Log: Provider [ Name] = ".NET Runtime", EventID = 1023; Event data: Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 7399A72F (73890000) with exit code 80131506. Provider [ Name] = "Application Error", EventID = 1000; Event data: devenv.exe | 12.0.31101.0 | 54548724 | clr.dll | 4.0.30319.34014 | 52e0b784 | c0000005 | 0010a72f | efa0 | 01d064df50b75c64 | C:\ProgTools\VisualStudio2013\Common7\IDE\devenv.exe | C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll | 1fb79138-d0e3-11e4-8263-b8763f0a6148 Provider [ Name] = "Windows Error Reporting", EventID = 1001; Event data: 73656369917 | 1 | APPCRASH | Not available | 0 | devenv.exe | 12.0.31101.0 | 54548724 | clr.dll | 4.0.30319.34014 | 52e0b784 | c0000005 | 0010a72f | C:\Users\dmcgaughran\AppData\Local\Temp\WER5BBA.tmp.WERInternalMetadata.xml | C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrashdevenv.exe8be03468606e212652d52dd2fbc8a338846a372ee1d7610613a381b1 | 0 | 1fb79138-d0e3-11e4-8263-b8763f0a6148 | 0 | fda09dd5a24c6c3bca5aaf4904a4aa21 [WER file attached] Provider [ Name] = "Application", EventID = 0; Event data: Error Handler Exception: System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.PipeException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes) --- End of inner exception stack trace --- at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ConnectionStream.EndRead(IAsyncResult asyncResult) at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult) --- End of inner exception stack trace --- at System.Net.Security.NegotiateStream.EndRead(IAsyncResult asyncResult) at System.ServiceModel.Channels.StreamConnection.EndRead() --- End of inner exception stack trace --- at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message) at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext) at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext) \r\n at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message) at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext) at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext) [4 occurrences at same timestamp] |
|
|
|
|
Thanks for the updates, sorry this is still an issue - we will continue to see if we can track this down, unfortunately we are not able to reproduce it so thats making it a bit tricky to verify the impact of any changes. Ill let you know when we have another round of updates out which might address this.
|
|
|
|
|
Hi Jeremy, As per my thread on this, http://www.mindscapehq.com/forums/thread/1801773 ... I have just updated to the latest LightSpeed nightly release from 23rd March 2015. But, I still seem to be having the same crashing issues as well. Right after updating, I opened a project and opened an lsmodel, I made a change to an entity, by adding a one to many join and made it nullable and also made it eager load for both backreference and collection (I was just playing, I know this isn't possible :) ) Anyway, at this point I have not saved the model, and I just pressed CTRL+SHIFT+B to build - The expected errors appeared in the Error List about a recursive association and VS crashed. As usual there is nothing in the Mindscape folder or the activity log. After VS restarted, I went through the same steps again - but it didn't crash this time. I'm not sure if any of this is helpful in where there might be issues, in that the Error List was populated before it crashed, I didn't get a chance respond to or notice if it was even there for the message box that pops up asking if you want to save anyway. Once VS did restart the file was not saved and VS had not made a recovery version either. I think the pattern seems to be related to saving/building somehow while the designer is open. Cheers, Sean |
|
|
|
|
Any updates on this - still happening and it's driving me mad as well as losing work every time it crashes. |
|
|
|
|
No unfortunately we have not been able to reproduce this yet to be able to identify whats needed to fix this.
|
|
|
|
|
Hi Jeremy, This is still happening - just now it was temporarily reproducible as well... I had an ls model open on another screen, it was just for viewing - hadn't made any changes to it. VS Crashed while I was going to a definition. Now this doesn't sound like it would be LS - but since I usually have these problem only when an LS model is open.... VS auto restarted, and I open the solution again - the lsmodel auto reopened on the other monitor and a few seconds later VS crashed again. Restarted, and same as above then crashed again. Restarted and I closed the LS Model as soon as it appeared. This time it everything was fine. The event logs shows similar as usual, a .net runtime error followed by application error... The .net error is...
I assume LS is using RayGun? Is that getting a chance to report anything? Cheers, Sean |
|
|
|
|
We do use Raygun in LightSpeed but for these types of errors it appears the process gets killed (and so no error is sent) as it would appear it is an unmanaged exception thats causing this, so likely due to something blowing up in the underlying COM calls being made. I can check though if you can ping me your machine name and the rough time when this occurred via email (support at mindscape.co.nz).
|
|
|
|
|
This crashing issues has been an issue for years :( It is extremely frustrating and I almost can't believe you are unable to reproduce it because it happens on 4 of 4 developer PCs here! How can we help you narrow this issue down? You can have remote access to my PC and I can show you the error in less than 5 minutes. |
|
|
|
|
If you can send us through a model file and a set of steps to reproduce this (e.g. open/close model repeatedly until it crashes) that would be ideal. You can email this through to support at mindscape.co.nz. Thanks for the offer of remote access but this isn't really practical as we would need to run through this repeatedly with a debugging session attached to trace this.
|
|
|
|
