all groups > dotnet clr > march 2006 > threads for march 29 - 31, 2006
Filter by week: 1 2 3 4 5
Constant unification - what's the best approach?
Posted by Ole Nielsby at 3/31/2006 10:02:24 PM
I need a mechanism for unifying constant objects.
Sort of like a generalization of String.Intern.
The constants can be nested (think pure Lisp or
immutable DOM).
I need a kind of weak-reference dictionary, so that
garbage constants will automatically be removed.
At present, the best id... more >>
Is there an ordering of objects?
Posted by Ole Nielsby at 3/31/2006 8:25:11 PM
When gc-able objects are created, this happens at
increasing (or decreasing) addresses.
Is the ordering of these addresses guaranteed to stay the same?
Or can an object be moved past another during compacting,
as a result of pinning or gc optimization techniques?
A scenario might look like:... more >>
"invalid handle", sockets, threads and garbage collector
Posted by Jan Waga at 3/31/2006 7:03:50 AM
Hello,
I'm working on two bugs in my app. They seemed unrelated at first glance,
but after some testing and searching the web for clues I am now sure they
are somehow connected. The two pieces of code execute frequently, at regular
intervals (this is a monitoring app) and sometimes - just s... more >>
as operator
Posted by Jiho Han at 3/30/2006 5:11:44 PM
I am not sure if this is the right group but I didn't see languages group.
I have the following statement:
if (e.SourceRow["COL1"] as string != e.TargetRow["COL2"] as string)
{
// do something
}
The COL1 and COL2 are both double type. e.SourceRow is System.Data.DataRow
and the ind... more >>
Locating thread locking issues
Posted by Sam at 3/30/2006 12:38:16 PM
I have a multi threaded app that seems to have a thread locking issue.
Are there any tutorials and tools that describe how to go about tracking
this ? I looked at the CLR profiler but that seems to be focussed more
on the heap and memory usage.
Any pointers ?
=sam... more >>
Confusing networking exception
Posted by Jeffery Jones at 3/30/2006 9:48:38 AM
Given - .NET 2.0, App 1 creates a TCP listening socket on 127.0.0.1
App 2 connects to the same socket on 127.0.0.1.
All works fine until the app is installed on another machine without
Visual Studio. Then the connecting client gets -
---- UnauthorizedAccessException ---------
Mess... more >>
|