Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vala
vala
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 702
    • Issues 702
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 39
    • Merge Requests 39
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GNOME
  • valavala
  • Issues
  • #42

Closed
Open
Opened Aug 25, 2009 by bugzilla-migration@bugzilla-migrationReporter

Should clean up class fields in class/base_finalize

Submitted by Sebastian Dröge @sdroege

Link to original bug (#592974)

Description

Hi, currently the memory managment features of vala are not applied to class fields. These should be cleaned up in class/base_finalize.

Example:

public class Test : GLib.Object {
  private class Foo foo = new Foo();
}

public class Foo : GLib.Object {

}

public void main() {
  new Test ();
}

Here the foo instance should be cleaned up in class_finalize. It might be a problem to detect where to clean up though, if fields are assigned

  • from instance/class/virtual methods or static ctors they should be cleaned up in base_finalize of the corresponding class and
  • if they're set in static methods, class ctors or are directly initialized (above example) they should be cleaned up in the class_finalize of the corresponding class.

Version: 0.7.x

Edited Oct 22, 2019 by Rico Tzschichholz
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
1.0
Milestone
1.0
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/vala#42