Ever since I upgraded my project and version of Unity from 5.6.0 to 5.6.1 the file and line in which the debug message or error occurred would not show up. This included double clicking the message, which wouldn't take me to the location of the error either.
After suffering for weeks I found the answer to this problem while writing this post. The solution is to expand the top right menu of the console tab, Stack Trace Logging > All and choose ScriptOnly. This works for Visual Studio 17 and MonoDevelop.
Related
When I highlight a file and hit F2, the file is normally replaced with an edit box where you can rename it.
After a few seconds, the edit box goes away and you need to quickly type the different file name (every time). I'm not sure what could cause this - any idea?
I'm on Ubuntu 20.04.1 LTS, Visual Studio code 1.52.1
Thanks
This looks like a bug reported in a few issues since v1.52 that all point to this one:
https://github.com/microsoft/vscode/issues/111652
also https://github.com/microsoft/vscode/issues/112555 and https://github.com/microsoft/vscode/issues/112438
It is reported in 111652 as fixed in the Insiders' Build. Can you test it there? I can't reproduce in Stable Build, W10.
I have Visual Studio Code version 1.22.2 running on Windows. When working on Javascript code, it crashes and causes a blue screen with the following technical info:
STOP: 0X0000007E
mfeavfk.sys - Address <...>
I have a plugin for MS SQL and a beautify plugin installed.
I recently updated Windows and started experiencing BSODs every time I started VS Code. Here's how I fixed it - hopefully this helps someone else:
Open a command prompt and type the following command:
code --disable-extensions
If your computer doesn't BSOD after this step, then an extension is likely causing the issue.
Press ctrl+shift+x to open the extensions sidebar
Under disabled, uninstall any extensions you aren't using or don't recognize.
Restart VS Code, and see if it still crashes.
If step 3 didn't help, try removing all extensions and then reinstalling one at a time until you find one that causes the crash. Then repeat steps 1-4, this time removing the extension you identified as causing the crash.
When I hit the code to create a break point. I am getting error saying that unable to toggle breakpoint eclipse marker id not found.
This has been reported here at bugs.eclipse.org.
The report says the affected version is 4.7.1a. The status of the bug is RESOLVED FIXED in v4.8, so we still encounter this issue with the version 4.7.3a (which is the current while writing).
As a workaround, you can close and reopen the GUI, this makes things normal again.
As a workaround, just close the specific java file in Eclipse editor and open it again.
Eclipse seems to be crashing all the time since I've upgraded to the Mac OS X Lion. The error I keep getting is stackoverflow.
I am using eclipse version: 1.3.1.20100916-1202 and have an open Android project at the moment of the crash. Where do I find the log file? What could be causing the crash?
I don't know enough about what has changed in Lion to determine the cause of the crash. But, here's how to find the logfile:
Window > Show View > PDE Runtime > Error Log. This gives you a view with the contents of the .log file.
Help > About Eclipse Platform > Configuration Details. This prints out a great number of details about the environment and also concatenates the .log file. Great for including in a bug report.
Locate the file yourself, see workspace/.metadata/.log.
Start Eclipse using -consoleLog. This will print the messages that normally go to the .log file in the enclosing shell/command window.
I'm trying to add Aptana to my Eclipse installation. I'm trying to do so on Win7 x64. I've tried both x86 and x64 versions of Eclipse. Most of the time Eclipse would install just fine, run okay, but as soon as I try to pluin Aptana it has problems. It will start up, then encounter an error immediately and close. Right now I have the x64 version installed fine. When I start it up it throws the error but doesn't close. I can close the error window and continue using Aptana just fine. I've attached a couple screenshots to show what the error is and what my current Installation Details look like. Let me know if there's any other information I could provide.
Thanks in advance.
Aaron-
Open the 'Error log' view, you probably see the stack of the NPE.
Then try to google the solution.