html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/3041#issuecomment-884213547,https://api.github.com/repos/pydata/xarray/issues/3041,884213547,IC_kwDOAMm_X840tAcr,26384082,2021-07-21T14:00:50Z,2021-07-21T14:00:50Z,NONE,"In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the `stale` label; otherwise it will be marked as closed automatically
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,460254571
https://github.com/pydata/xarray/issues/3041#issuecomment-511136084,https://api.github.com/repos/pydata/xarray/issues/3041,511136084,MDEyOklzc3VlQ29tbWVudDUxMTEzNjA4NA==,2783717,2019-07-13T16:38:14Z,2019-07-13T16:39:25Z,NONE,">  Apparently in CPython this happens if you have a reference cycle.

AFAIK this is no longer true after Python 3.4.

I took a look with @delandmeterp and found that manually adding a `gc.collect()` (which collects all cycles) after deleting `temp` fixes the issue. The cycle was keeping the object around longer than expected, resulting in the lock error. It's not clear to me where the cycle is coming from (I'm not familiar with xarray internals), but this is indeed the issue.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,460254571
https://github.com/pydata/xarray/issues/3041#issuecomment-511130022,https://api.github.com/repos/pydata/xarray/issues/3041,511130022,MDEyOklzc3VlQ29tbWVudDUxMTEzMDAyMg==,31093031,2019-07-13T15:20:39Z,2019-07-13T15:20:39Z,NONE,"I'm trying to figure that out now.
On xarray master, the above test does not break anymore. But if you add a third `temp.compute()` call, it occurs again.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,460254571
https://github.com/pydata/xarray/issues/3041#issuecomment-507055108,https://api.github.com/repos/pydata/xarray/issues/3041,507055108,MDEyOklzc3VlQ29tbWVudDUwNzA1NTEwOA==,1217238,2019-06-30T17:58:44Z,2019-06-30T17:58:44Z,MEMBER,"I did a little bit of testing. It appears that in the case of the double call to `temp.compute()`, `temp.__del__` is never called. Apparently in CPython this happens if you have a reference cycle. I'm not quite sure what the source of the reference cycle is here (or why it only appears when calling  compute twice), but that seems to be the likely culprit.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,460254571
https://github.com/pydata/xarray/issues/3041#issuecomment-505494480,https://api.github.com/repos/pydata/xarray/issues/3041,505494480,MDEyOklzc3VlQ29tbWVudDUwNTQ5NDQ4MA==,1217238,2019-06-25T15:23:39Z,2019-06-25T15:23:39Z,MEMBER,"Xarray does its best to automatically close files when they are no longer necessary, but this is pretty challenging to do in  general. You are generally best off either explicitly closing files or not rewriting the same filenames.

In this particular case,  I suspect that the second call  to `temp.compute()` means that the  file manager opened by `xr.open_dataset('test.nc')` can't get garbage collected, for some reason. I'm  not entirely sure what's  going on, but see these lines in `CachingFileManager` if you want to go into the gory details:
https://github.com/pydata/xarray/blob/76adf1307cb15d63521b40408a569258bacd3623/xarray/backends/file_manager.py#L190-L218","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,460254571