Skip to content
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

"Attempted to access an unloaded AppDomain" during Roslyn.Services.Editor2.UnitTests.dll #15497

Closed
jasonmalinowski opened this issue Nov 23, 2016 · 15 comments · Fixed by #49355
Closed
Assignees
Labels
Area-IDE Bug Flaky Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented Test Test failures in roslyn-CI
Milestone

Comments

@jasonmalinowski
Copy link
Member

At the end of the xunit log:

Finished: Roslyn.Services.Editor2.UnitTests
System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain.

Unfortunately no additional output or crash dump was produced.

@Pilchie
Copy link
Member

Pilchie commented Nov 23, 2016

This doesn't seem actionable without more info. Let's wait a bit to see if it starts to happen more.

@Pilchie Pilchie closed this as completed Nov 23, 2016
@Pilchie Pilchie added the Resolution-Not Reproducible The described behavior could not be reproduced by developers label Nov 23, 2016
@jasonmalinowski
Copy link
Member Author

@Pilchie This is the second time it's happened in recent (last week or two) memory.

@Pilchie
Copy link
Member

Pilchie commented Nov 23, 2016

So - what do you propose doing about it?

@jasonmalinowski
Copy link
Member Author

Figure out why we didn't get a crash dump or something?

@jasonmalinowski jasonmalinowski removed the Resolution-Not Reproducible The described behavior could not be reproduced by developers label Dec 14, 2016
@Pilchie Pilchie added this to the 2.0 (RTM) milestone Dec 15, 2016
@Pilchie
Copy link
Member

Pilchie commented Dec 15, 2016

Can you think of what additional logging we could add to track this down?

@jasonmalinowski
Copy link
Member Author

My main thought is xunit put that error message in the log....they must have caught the exception somewhere. It might have a stack trace that can be printed too.

@jasonmalinowski jasonmalinowski assigned dpoeschl and unassigned cston Jul 10, 2017
@jasonmalinowski jasonmalinowski modified the milestones: 15.3, 16.0 Jul 12, 2017
@jasonmalinowski
Copy link
Member Author

Moving to 15.3, since we're now seeing this very, very reliabily.

@mavasani
Copy link
Contributor

@sharwell sharwell added the Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented label Nov 13, 2020
@sharwell sharwell self-assigned this Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE Bug Flaky Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented Test Test failures in roslyn-CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.