Abstract: A method for managing objects stored in memory is presented. The method may include receiving, by a memory allocator in a garbage collected system, a first free memory chunk. The method may include creating a node to associate with the first free memory chunk and ensuring that a first memory region containing the node will be considered to be free memory during a sweeping phase of the garbage collected system.

Abstract: Examples disclosed herein relate to pointers in a memory managed system. A garbage collection thread in a garbage collection system indicates via a first indication, that the garbage collection system has entered a marking phase, the garbage collection system managing a heap of memory. The garbage collection thread attempts to modify a conversion status variable, associated with a mutator thread belonging to a set of mutator threads associated with the garbage collection system, from a first conversion status value, indicating that the mutator thread is performing a weak pointer conversion operation, to a second conversion status value indicating that a handshake is required between the garbage collection thread and the mutator thread. The garbage collection thread determines that the conversion status variable does not contain the second conversion status value. The garbage collection thread determines that a set of pointers is empty.

Abstract: A method for managing objects stored in memory is presented. The method may include receiving, by a memory allocator in a garbage collected system, a first free memory chunk. The method may include creating a node to associate with the first free memory chunk and ensuring that a first memory region containing the node will be considered to be free memory during a sweeping phase of the garbage collected system.

Abstract: Examples disclosed herein relate to pointers in a memory managed system. A garbage collection thread in a garbage collection system indicates via a first indication, that the garbage collection system has entered a marking phase, the garbage collection system managing a heap of memory. The garbage collection thread attempts to modify a conversion status variable, associated with a mutator thread belonging to a set of mutator threads associated with the garbage collection system, from a first conversion status value, indicating that the mutator thread is performing a weak pointer conversion operation, to a second conversion status value indicating that a handshake is required between the garbage collection thread and the mutator thread. The garbage collection thread determines that the conversion status variable does not contain the second conversion status value. The garbage collection thread determines that a set of pointers is empty.

Abstract: In one example in accordance with the present disclosure, a method may include identifying, by a first operating system process in a computer system accessing a shared memory heap, a first object at a first memory address in the shared memory heap. The first object may have been previously allocated in the shared memory heap by a second operating system process. The method may also include identifying an object descriptor associated with the first object at a second memory address in the shared memory heap. The object descriptor occupies a number of bits of memory independent of the type. The method may also include determining a size of the first object based on the object descriptor, enumerating, based on the object descriptor, fields associated with the first object and performing an action based on each field of the enumerated fields.

Abstract: In one example in accordance with the present disclosure, a method for managing objects stored in memory may include identifying a first object in a heap. The heap may be accessed by a plurality of mutator threads executing within a first plurality of operating system processes. The method may also include determining that the first object is a reachable object and determining that a first range of memory locations in the heap does not contain any reachable object. The method may also include receiving an allocation request from a second mutator thread from the plurality of mutator threads and allocating a first free chunk of memory including at least a part of the first range of memory locations to the second mutator thread.

Abstract: In one example in accordance with the present disclosure, a method for managing objects stored in memory may include identifying a first object in a heap. The heap may be accessed by a plurality of mutator threads executing within a first plurality of operating system processes. The method may also include determining that the first object is a reachable object and determining that a first range of memory locations in the heap does not contain any reachable object. The method may also include receiving an allocation request from a second mutator thread from the plurality of mutator threads and allocating a first free chunk of memory including at least a part of the first range of memory locations to the second mutator thread.

Abstract: In one example in accordance with the present disclosure, a method may include identifying, by a first operating system process in a computer system accessing a shared memory heap, a first object at a first memory address in the shared memory heap. The first object may have been previously allocated in the shared memory heap by a second operating system process. The method may also include identifying an object descriptor associated with the first object at a second memory address in the shared memory heap. The object descriptor occupies a number of bits of memory independent of the type. The method may also include determining a size of the first object based on the object descriptor, enumerating, based on the object descriptor, fields associated with the first object and performing an action based on each field of the enumerated fields.