-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Regression] Immediate editor crash on opening project #20011
Comments
Still happening with 1fc7973 and deleting |
To add a data point I am unable to reproduce this issue with 1fc7973 on my local machine (windows 7 64-bit, mono 5.12.0.226, VS2017 15.6.27428.2043). My test included opening a couple of existing mono projects and confirming they can build and run successfully. |
For Debian Stretch, Mono Version 5.10.1.20 and commit de910f8 problem still exists.
Debug info from gdb:
|
I think I was mistaken when I said above that the error about I did more tests today and found that the crash apparently is related to that problem. I suppose it's been not fatal before recent changes for some reason, but now it's causing Godot to crash. On a side note, the same error message appears if I build my project I'll try to go deeper and share what I find later. |
@mysticfall I can check what is used. |
As a workaround, I found that copying 15.x version of |
Godot uses msbuild 15.4.0.0 ( Wed Nov 29 14:56:11 UTC 2017). |
@akien-mga If there are other users who are affected by this problem, maybe we should add this to the |
This crash is happening to me on Linux Manjaro Hakoila, it became really annoying in Godot 3.0.6. Each time I need to run the code, I need to:
In Godot 3.0.5 it also happened, but the editor would not crash all the time, and then deleting the As for the error, I get the same stacktrace described above minus the "Version" attribute part. I'm using msbuild version I really hope you fix it soon, because like I said these crashes are destroying the user experience. |
CC @neikeq |
Does this happen with any project? A new one for example (after generating the solution). |
This looks like a duplicate of #15386. I'm planning GodotSharpTools to use nuget Microsoft.Build packages instead. |
@neikeq I haven't tested it with a new project yet, but I believe it only happens when the <PackageReference Include="Ensure.That" Version="8.0.0" /> In that case, I think it wouldn't be reproduced with a newly create project but the suggested change with |
I think I should also mention I'm using Paket package in my project.
…On Fri, Aug 24, 2018, 11:23 Xavier Cho ***@***.***> wrote:
@neikeq <https://github.com/neikeq> I haven't tested it with a new
project yet, but I believe it only happens when the .csproj contains a
package reference like this:
<PackageReference Include="Ensure.That" Version="8.0.0" />
In that case, I think it wouldn't be reproduced with a newly create
project but the suggested change with Microsoft.Build packages would fix
the problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20011 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEwqYT0Og4E5laU7jP6Vasg2lzRgJ9Ajks5uT7gWgaJpZM4VGK5b>
.
|
Is this still reproducible in the current master branch or latest beta build? |
This is a duplicate of #15386, no? |
Godot version:
master
/ 9f82368OS/device including version:
Manjaro Linux 17.1
Issue description:
When opening a C# project with the latest build of Godot, it immediately crashes with the following output:
I'm pretty sure that the(Edit : Upon further testing, it looks like this could be the real cause but just stopped being harmless since recent changes. I'll add comments after doing more tests.)InvalidProjectFileException
is not the real cause of the problem, since it's been always there ever since I started using Godot (#15386).This seems to be a regression, since it started to happen after I upgraded from 0ffec7d to 9f82368. And after I rolled back my build to 0ffec7d, the editor started to work without a problem again.
The text was updated successfully, but these errors were encountered: