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
|
Hi Guys, When using Visual Studio 2013 currently, but also happens on 2012 and 2010 - it totally crashes and shuts down frequently when using the Lightspeed designer view. This is happening on multiple Win7 x64 PCs, even on a brand new Win8 x64 build. This has been happening for sometime too. I have tried disabling other addins (such as .net demon which does not work well with Lightspeed) and Resharper - but am still getting the same issues. I have tried uninstalling and reinstalling LS, and as mentioned above even rebuilt a PC with Win8. The problem also happens using different models, albeit they are not very simple ones. Anyway - is there any activity log that LS may keep so I could get any ideas what else may be causing this? The event log just says...
And the %AppData%\Microsoft\VisualStudio\12.0\ActivityLog.XML doesn't contain anything either (as in nothing recent) Any pointers for more info? Cheers, Sean |
|
|
Check for a AppData\Local\Mindscape folder in your users folder and check for any lsmdlog_*.txt files there. If there is one matching from the date of the crash could you send through the contents please.
|
|
|
Hi Jeremy, It's just happened again on my Win8 machine, I don't have any Mindscape folder in any of the AppData folders? Have searched for files named lsmdlog_* but nothing is found. Cheers, Sean |
|
|
Hi Sean, Thanks for checking - Ive made a change which will be in the next nightly build which may address this and failing that should hopefully help provide a bit more logging we can use to track down the problem. Let me know if you continue to see this after updating.
|
|
|
Hi, I don't know if this helps but after the same thing happened to me this morning VS2012 and latest Lightspeed. I reloaded the project to find that the Mindscape assemblies has not been added to the project references and on searching through the GAC and Program Files/Mindscape folder I cannot find them anywhere. Additional information which might be important: 1) the solution is .NET 4.5 2) running win 8.1 3) searched whole drive c: and no dlls for Mindscape anywhere. Clive |
|
|
I've been running into the same problem for a while now. Sometimes Lightspeed 5 will crash in Visual Studio 2013 when it is loading the model, sometimes it will crash when saving the model, and sometimes it will crash VS after I've closed and I'm working in something else (usually when I'm saving). My workaround has been to edit the model then close and reopen VS to ensure that it doesn't crash while I'm working on something critical. Recently I tried to collected detailed information from VS2013 by opening it from the Dev. Command Promt with Logging on. Unlike every other time I've run the Lightspeed model I was working in the model for about 2 hours and VS didn't crash once. But when I turn logging off VS will crash at some point after opening a model file. Unfortunately because of this I can't get a detailed log of what is going on. But I thought this additional information might be helpful. |
|
|
Have you tried the latest nightly build? While I have been working much less in the model recently - I can only recall it crashing once when saving the model. So the latest build may have fixed some of the issues. |
|
|
Spoke too soon, this has just crashed two times in a row for me. First time was updating database from model and crashed - the DB was updated. Second time was saving the model and crashed - the model was not saved. VS ActivityLog.XML does exist. LS lsmdlog_20140504.txt only contains a couple of exceptions from 2 weeks ago - I can post here/send them over if needed (although I guess RayGun would have recorded them : ) Cheers, Sean |
|
|
Once a week I install the latest nightly build and after Evan responded a few weeks ago about trying to fix this issue I installed that nightly build. This didn't seem to resolve the issue. |
|
|
If there are any repeatable steps for triggering this please let us know.
|
|
|
Hi Jeremy, This is still happening, the only real repeatable step is that an lsmodel is open. It could happen when pressing F5, is could happen when saving a file, it could happen when closing file - it's all seemingly random, I still have an incling it somehow related to .net demon as well - but I have tried disabling that before and still had the issue - I will try disabling again. But in the mean time with the constant crashes, is there any logs I can provide? There is nothing in AppData\Local\Mindscape or ActivityLog.XML Cheers, Sean |
|
|
Unfortunately i also experience these crashes and there are no specific steps to reproduce them. Sometimes crash happens on save, sometimes on build, in vs2012 and vs2013. |
|
|
A there anything more that we can do to help fix this issue? |
|
|
Only the same as Ive mentioned above Im afraid, which is if there are any repeatable steps for triggering this please let us know.
|
|
|
Am i understood correctly, that not every user experiences this problem, but a small part of users? |
|
|
Yes, thats correct
|
|
|
Good day. Yesterday i reinstalled Windows (clean install of Windows 8.1 (EN-US) with all updates, Visual Studio 2015 Community, LightSpeed ORM 5.5, SQL Server 2014 LocalDB). Today i got crash while viewing LightSpeed model in Visual Studio. So i think that these crashes are not related to some 3rd party addons, etc. I have no antivirus or firewall software installed (Windows Defender is disabled). Can it be caused by usage of SSD drive for the system or non-English regional settings or multiple input methods (English/Russian/Ukrainian)? Can it be caused by install of SQL Server Management Studio 2014? (I noticed that LightSpeed installer offers to install designer not only for VS2015 but also for VS2010 if SSMS is installed)? |
|
|
Here is some VS2015 logs. I hope this will help. There are still no specific steps to reproduce. I open solution, then open/close, open/close source files and/or LightSpeed model until Visual Studio crashes.
|
|
|
Fresh install of Win 8.1 Enterprise, VS 2013 update 5, Lightspeed 5.0 nightly... Opened a solution, opened the ls model to activate, entered details, saved, went to close the file in vs > crash. Same errors in the eventlog as the other guys
.. also nothing in ActivityLog.XML |
|
|
It wont be due to an SSD or SQL Management Studio being installed. The exception points to heap corruption, which is likely due to unmanaged code causing the corruption (e.g. could be from the Visual Studio DSL tools we leverage), unfortunately this is very difficult to pinpoint as we cannot debug Visual Studio itself and the exception call-site most likely wont be related to the cause at all. This may also be the cause: https://support.microsoft.com/en-us/kb/2679415
|
|
|
ImagesInSpace, Do you use notebook or PC? |
|
|
Mini PC, brand new Intel NUC5i5MYHE http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i5myhe-board-nuc5i5mybe.html http://ark.intel.com/products/84861/Intel-NUC-Kit-NUC5i5MYHE |
|
|
I ask everyone who also experience there crashes to post your software (os version, language) and hardware configuration to this thread. Maybe we will be able to find the reason. Thanks. |
|
|
I disabled parallel GC by adding
to the devenv.exe.config and this did not help. |
|
|
Today i installed 32-bit version of Windows 8.1 (with VS2015 and LS 5.5), and this is also didn't help. So these crashes are in both 32-bit and 64-bit Windows. |
|
|
Good day. Are there any updates on this issue? |
|
|
Nothing positive Im afraid. We have managed to get some more information on these crashes however the crash is being triggered by Visual Studio itself and it appears that it would be being caused originally by a bug in the underlying DSL tools for Visual Studio in cleaning up some of the resources. The DSL Tools are what we use to provide the designer. At this stage we are still trying to figure out how to reproduce this reliably.
|
|