-
Notifications
You must be signed in to change notification settings - Fork 4
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
Remarker appears to be the cause of crashes in VS 15.8 #6
Comments
I've experienced the same problem. Here is the relevant ActivityLog.xml entry: 1310 2018/08/16 17:03:38.759 Error |
Can confirm this is happening to me as well. ActivityLog says the same thing as above : |
@seangifford or @stefangavrilasengage |
Repro Steps:
Expected: Actually: |
I can confirm the same issue. Any progress figuring out a solution? I miss it! |
I uninstalled & reinstalled a previous version to make this work and it does the job (currently using 15.7.6). |
I confirm it too |
Any update on this, and does it crash on 15.9.x? |
I just updated to 15.9.4 and tried again, but the issue still remains |
Thanks for this link @tgaldi and to @negrutiu for the work. It feels such a shame to have to switch from a package on the VS marketplace to downloading a vsix from github but given that @jgyo has been so silent on this critical bug I guess it's the only option. I haven't tried it out yet and will review the commits to make sure that one of the very sensible looking commits doesn't include a bitcoin mining bot or whatever, but I assume you can vouch that it works @tgaldi? |
Hey guys, I didn't know about this thread... |
With the Remarker extension enabled, VS crashes upon trying to open any SLN.
I disable Remarker, VS stops crashing upon opening any SLN. Re-enabling Remarker gets VS to crash again. Not sure who is at fault here, but trying to be helpful by reporting to both parties involved.
VS Error Report:
https://developercommunity.visualstudio.com/content/problem/311694/extensions-that-fail-to-load-crash-visual-studio.html
Thanks!
The text was updated successfully, but these errors were encountered: