gregoryyoung1 at gmail.com
Mon Jan 12 22:42:36 UTC 2015
I have one I can file. I figured it was something on my side though.
Could it be the FileHandle closing itself later for a second time? Are
there other scenarios aside from close this can happen on?
In general SafeFileHandle is pretty painful to use since none of the
definitions support it.
Want me to create an issue?
On Tue, Jan 13, 2015 at 12:32 AM, Zoltan Varga <vargaz at gmail.com> wrote:
> This is a bug, it shouldn't happen. If you have some kind of reproducible
> test case, please file a bug report with it.
> On Mon, Jan 12, 2015 at 5:28 PM, Greg Young <gregoryyoung1 at gmail.com> wrote:
>> _wapi_handle_unref_full: Attempting to unref unused handle 0x8a
>> I seem to be getting this message from the runtime not sure what could
>> be causing it. From some googling this appears to happen when you
>> close a file handle multiple times.
>> The only place close is called is :
>> protected override void Dispose(bool disposing)
>> if(_handle == null) return;
>> _handle = null;
>> Not sure how it could be called multiple times. I don't get any issues
>> on the CLR.
>> Any ideas?
>> Studying for the Turing test
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
Studying for the Turing test
More information about the Mono-devel-list