After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728571 - Base class cycle causes endless loop that eats whole RAM
Base class cycle causes endless loop that eats whole RAM
Status: RESOLVED OBSOLETE
Product: vala
Classification: Core
Component: Code Generator
0.22.x
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2014-04-19 19:30 UTC by Marcin Lewandowski
Modified: 2018-05-22 15:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
resolver: Avoid cycles during is_subtype_of (1.78 KB, patch)
2014-09-10 21:15 UTC, Florian Brosch 		none Details | Review
Break base struct cycles during get_type_for_struct (2.88 KB, patch)
2014-09-10 21:25 UTC, Florian Brosch 		none Details | Review

Description Marcin Lewandowski 2014-04-19 19:30:01 UTC 
Today I've mistakenyl caused base class cycle. Compiler has detected it but instead of breaking compilation it has eaten memory unless was OOMed by kernel.

Error message was:

src/daemon/pipeline/node/source/file/single/source-file-single-base.vala:11.30-11.33: error: Base class cycle (`Source.File.Single.Base' and `Source.File.Single.Base')
  public class Single.Base : Base {


vala 0.22.1
Comment 1 Florian Brosch 2014-09-10 21:15:53 UTC 
Created attachment 285865 [details] [review]
resolver: Avoid cycles during is_subtype_of
Comment 2 Florian Brosch 2014-09-10 21:25:02 UTC 
Created attachment 285866 [details] [review]
Break base struct cycles during get_type_for_struct

I am not happy with this one. Any suggestions?
Comment 3 GNOME Infrastructure Team 2018-05-22 15:08:52 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vala/issues/444.