GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

teknomunk (teknomunk@apogee.polaris-1.work)'s status on Tuesday, 16-Apr-2024 11:24:01 JST

  1. Embed this notice
    teknomunk (teknomunk@apogee.polaris-1.work)'s status on Tuesday, 16-Apr-2024 11:24:01 JST teknomunk teknomunk
    in reply to
    • karna :flipflop: :buffsuki:
    • binkle
    • hazlin no plap pirate
    @karna @binkle @hazlin

    Going to drop in here to give what I know about the subject. I don't have any particular insight into python.

    When using referencing counting, you can release the memory to the allocator as soon as they reach zero references or you can queue them up for later releasing. This works reasonably well, but as you pointed out: cycles exist and make reference counting fail.

    A tracing garbage collector is one of the solutions for automaticly releasing memory that is no longer needed. It traces the graph of every memory allocation that is still reachable from global variables and the stack and marks everything that is reachable and throws away everything else.

    As I under it, python mostly uses reference counting, but falls back to a tracing garbage collector for dealing with cycles.
    In conversation Tuesday, 16-Apr-2024 11:24:01 JST from gnusocial.jp permalink

Feeds

  • Activity Streams
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.