Sysprogs forums › Forums › VisualGDB › CppEngineHost is hanging up frequently
- This topic has 11 replies, 6 voices, and was last updated 8 years ago by support.
-
AuthorPosts
-
February 25, 2016 at 15:19 #7685kbzowskiParticipant
Hi, I noticed, that since last update of VisualGDB CppEngineHost is hanging up more often (CppEngineHost has stopped working). Where I can find logs to diagnose what is causing this?
Best regards,
Krzysztof Bzowski- This topic was modified 8 years, 10 months ago by kbzowski.
February 28, 2016 at 19:43 #7695supportKeymasterHi,
You can replace the CppEngineCore.dll file with a debug build from http://sysprogs.com/files/tmp/CppEngineCore.dll, create a dump file via Task Manager and send it to us. This way we should be able to see what is causing the crashes and fix them.
March 3, 2016 at 11:23 #7711kbzowskiParticipantIt is rather strange. After replacing dll with debugable version – all errors are gone…
I will continue my tests and report if it hang again.March 5, 2016 at 02:15 #7720supportKeymasterSure. Let us know once you have further information.
May 6, 2016 at 08:17 #8174marrtinParticipantThanks.
I have the same problem you have already sent me some debug version of CppEngineCore.dll but the intellisense engine didn’t work then at all.
This link is no more accessible. Can you send me please current debug version of CppEngineCore.dll. I really want to use clang intellisense, but I can’t. The engine with default installation of VisualGDB (5.1) still crashes in my project.
Thanks.
May 9, 2016 at 15:50 #8183Ken MacfarlaneParticipantHi,
I’m not sure if this is the same problem as I don’t know how to tell if its the CppEngineHost – the whole VisualStudio app hangs on startup every 2nd day or so. I can get round it by creating each new project in its own solution, in a new directory. The others around me who are more knowledgeable about VS than I am, reckon that the problem is the number of files that VS has to parse on startup due to having ~10 projects in my stmF7 solution, & that it could be fixed by deleting all of VS’s temporary files e.g. the .pdb’s & .vcxproj’s, but I haven’t tried this yet as I’m not convinced I’ve got all the files I need under Git yet!
May 9, 2016 at 22:27 #8190marrtinParticipantHi
I think that the problem is not the same. CppEngineHost runs in separate process. I don t know how big are your projects, but in my project there are far more system headers to parse and also additional libraries (STL, boost, etc…). But you are right, native intellisense need some times rebuild. Deleting its database file is safe and sure way. Neverthless I am not be able to persuade clang inntellisense to work properly. After some browsing and switching files simple crashes. And then crashes and restarts again.
Please help.
May 14, 2016 at 22:10 #8217supportKeymasterOK, we have just finished updating our IntelliSense engine to a newer version of Clang that should resolve many issues. Could you try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.7.713.msi?
June 11, 2016 at 16:16 #8393RaEyEParticipantHello,
currently I’m having the exactly same issue. Whenever I try to open a VisualGDB Project, after a few seconds I get the notification CppEngineHost.dll stopped running.
I already tried to repair / reinstall the currently newest version of Visual GDB (5.1r6) without any change.
Are there any news on the issue?
DumpFile of CppEngineHost.exe (32 bit): https://onedrive.live.com/redir?resid=10F7C8CBFF95CE79!58440&authkey=!AHJCAmn8cUQ2HxQ&ithint=file%2czip
June 11, 2016 at 17:44 #8394supportKeymasterHi,
We have fixed a few things in the engine since the latest 5.1 build, so please check if you can still reproduce the problem with this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.4.821.msi
If yes, please upload an updated dump file and we will look into it.
November 28, 2016 at 01:58 #9601stephenParticipantI am having the same problem. Version 5.2 Build 1297.
It happens every few seconds to few minutes while I am writing code. It is seriously starting to affect my workflow so any help would be appreciated.
BTW all the links above are broken.
Best regards
November 28, 2016 at 05:37 #9603supportKeymasterHi,
Sorry about that. Please send the dump file created by the IntelliSense engine via our support form and we will send you a hotfix (or a diagnostic build to pinpoint it better) within 48 hours.
The temporary build links automatically expire when their functionality is moved to the normal releases. If the same problem occurs with build 1297, it is probably caused by something else and we would need a dump file to pinpoint/fix it.
-
AuthorPosts
- You must be logged in to reply to this topic.