DotGNU Portable.NET - Bugs: bug #13443, static FileStream not written to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #13443: static FileStream not written to disk on exit without Close()
Submitter: | None | ||
Submitted: | Sat 18 Jun 2005 04:18:22 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Confirmed |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
Jump to the original submission
Sun 19 Apr 2009 10:00:07 PM UTC, comment #6: |
Thomas Uxiou <uxiou> |
Wed 16 Apr 2008 05:09:16 PM UTC, comment #5: http://anallesbiansex.pornlivenews.com/articles/301332/anal-lesbian-sex-in-the-toilet
|
Anonymous |
Fri 28 Mar 2008 09:58:52 AM UTC, comment #4: A relaxing way to download mp3 - http://mp-3.name
|
Anonymous |
Sun 26 Jun 2005 03:37:49 PM UTC, comment #3: The problem might be that static class members not garbage collected in ILExecProcessDestroy.
|
Klaus Treichel <ktreichel> |
Mon 20 Jun 2005 11:26:08 AM UTC, comment #2: just in case someone cares: I submited this bug, but wasn't logged in |
Erich Kitzmüller <ammoq> |
Sun 19 Jun 2005 11:02:17 AM UTC, comment #1: In the test case, the user declares the class member 's' as static. When compiled, the runtime doesn't appear to ever call the finalizer nor the Dispose(bool) method of the System.IO.FileStream class, even on application exit.
|
Deryk Robosson <drobosson> |
Sat 18 Jun 2005 04:18:22 PM UTC, original submission:
Look at the following example:
|
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-06-19 | drobosson | Status | None | Confirmed | |
2005-06-18 | None | Attached File | - | Added StreamTest.cs, #2613 |
Powered by Savane 3.13-f8d8.
Corresponding source code
Automatic deterministic resource release does not exist, short of an AppDomain unload and "using".
Mono and Pnet both try to minimize the number of orphan objects but there simply is no general way (circular dependencies ...) to do so.
Mono tries to finalize "static" objects but isn't deteministic in doing so (at least not obviously so from an application developer's POV).
Pnet doesn't even try to finalize "static" objects and is thus deteministic g.