Garbage collection basics in Compiler Design - Mini Project: Build & Apply

Garbage Collection Basics Database

📖 Scenario: You are building a simple database to track objects in memory for a garbage collector in a compiler design project. This database will help you understand how objects are allocated, referenced, and identified as garbage.

🎯 Goal: Create a database that stores objects with their IDs and reference counts, then identify which objects are eligible for garbage collection (those with zero references).

📋 What You'll Learn

Create a dictionary called objects with object IDs as keys and their reference counts as values.

Create a variable called threshold set to 0 to identify garbage objects.

Use a dictionary comprehension to create a new dictionary called garbage_objects containing only objects with reference counts equal to the threshold.

Add a final step to count the number of garbage objects and store it in a variable called garbage_count.

💡 Why This Matters

🌍 Real World

This project models how a garbage collector tracks and identifies unused objects in memory to free up space automatically.

💼 Career

Understanding garbage collection is important for compiler design, programming language development, and optimizing software performance.

1

Create the objects dictionary

Create a dictionary called objects with these exact entries: "obj1": 3, "obj2": 0, "obj3": 5, "obj4": 0, and "obj5": 2.

Compiler Design

# Create the objects dictionary with given IDs and reference counts
# Your code here

Hint

Use curly braces {} to create a dictionary with keys and values separated by colons.

2

Set the garbage threshold

Create a variable called threshold and set it to 0 to represent the reference count that identifies garbage objects.

Compiler Design

objects = {"obj1": 3, "obj2": 0, "obj3": 5, "obj4": 0, "obj5": 2}
# Create the threshold variable set to 0
# Your code here

Hint

Just assign the number zero to the variable threshold.

3

Identify garbage objects

Use a dictionary comprehension to create a new dictionary called garbage_objects that contains only the entries from objects where the reference count equals the threshold.

Compiler Design

objects = {"obj1": 3, "obj2": 0, "obj3": 5, "obj4": 0, "obj5": 2}
threshold = 0
# Create garbage_objects dictionary with objects having reference count equal to threshold
# Your code here

Hint

Use {key: value for key, value in dictionary.items() if condition} syntax for dictionary comprehension.

4

Count garbage objects

Create a variable called garbage_count and set it to the number of entries in the garbage_objects dictionary.

Compiler Design

objects = {"obj1": 3, "obj2": 0, "obj3": 5, "obj4": 0, "obj5": 2}
threshold = 0
garbage_objects = {obj_id: ref_count for obj_id, ref_count in objects.items() if ref_count == threshold}
# Count the number of garbage objects and assign to garbage_count
# Your code here

Hint

Use the len() function to count dictionary entries.

Practice

1. What is the main purpose of garbage collection in programming?

easy

A. To automatically free memory that is no longer used by the program

B. To speed up the execution of the program

C. To compile the program faster

D. To store data permanently on disk

Solution

1. Step 1: Understand what garbage collection does

   Garbage collection automatically frees memory that the program no longer uses, preventing memory waste.

2. Step 2: Compare options with this purpose

   Only To automatically free memory that is no longer used by the program describes this automatic freeing of unused memory, while others describe unrelated tasks.

3. Final Answer:

   To automatically free memory that is no longer used by the program -> Option A

4. Quick Check:

   Garbage collection = automatic memory freeing [OK]

Hint: Garbage collection frees unused memory automatically [OK]

Common Mistakes:

• Thinking garbage collection speeds up program execution
• Confusing garbage collection with compiling
• Believing garbage collection stores data permanently

2. Which of the following is a correct statement about garbage collection syntax in most programming languages?

easy

A. You declare garbage collection using gc start; in code

B. You must manually call a function named garbageCollect() to free memory

C. Garbage collection runs automatically without explicit syntax

D. Garbage collection is triggered by writing freeMemory() in the program

Solution

1. Step 1: Recall how garbage collection works in modern languages

   Most modern languages run garbage collection automatically without needing explicit calls or syntax.

2. Step 2: Evaluate each option

   Options B, C, and D suggest manual calls or commands that are not standard syntax; only A correctly states automatic operation.

3. Final Answer:

   Garbage collection runs automatically without explicit syntax -> Option C

4. Quick Check:

   Garbage collection = automatic, no manual calls [OK]

Hint: Garbage collection usually needs no manual commands [OK]

Common Mistakes:

• Assuming you must call garbage collection manually
• Looking for special syntax to start garbage collection
• Confusing garbage collection with memory free functions

3. Consider this pseudocode snippet:

var a = new Object()
var b = a
b = null
// Garbage collection runs here

Which object(s) will be collected by garbage collection?

medium

A. No objects will be collected because a still references the object

B. The object referenced by a and b

C. The object referenced by b only

D. Both a and b variables will be collected

Solution

1. Step 1: Analyze references to the object

   Initially, both a and b point to the same object. After b = null, only a references it.

2. Step 2: Determine if object is unreachable

   Since a still references the object, it is reachable and will not be collected.

3. Final Answer:

   No objects will be collected because a still references the object -> Option A

4. Quick Check:

   Object referenced = not collected [OK]

Hint: Object with any reference is not collected [OK]

Common Mistakes:

• Thinking object is collected when one reference is null
• Confusing variable collection with object collection
• Assuming variables themselves are garbage collected

4. Identify the error in this pseudocode related to garbage collection:

var x = new Object()
var y = x
x = null
// Garbage collection runs here
print(y.property)

What problem might occur?

medium

A. Syntax error due to missing garbage collection call

B. Runtime error because y is null

C. Garbage collector frees object causing y.property to fail

D. No error; object is still referenced by y

Solution

1. Step 1: Check references after x = null

   Even though x is null, y still references the object, so it remains reachable.

2. Step 2: Understand garbage collection behavior

   Garbage collection only frees objects with no references. Since y references the object, it won't be freed, so y.property is safe.

3. Final Answer:

   No error; object is still referenced by y -> Option D

4. Quick Check:

   Object referenced = no error [OK]

Hint: Object referenced by any variable is safe from collection [OK]

Common Mistakes:

• Assuming object is freed when one reference is null
• Expecting syntax error for missing manual garbage call
• Confusing variable null assignment with object deletion

5. In a program, you have a complex data structure where some objects reference each other in a cycle, but no external variables reference any of them. What will happen during garbage collection?

hard

A. Only some objects in the cycle will be collected, others remain

B. The cycle of objects will be collected because they are unreachable from outside

C. The cycle will never be collected because objects reference each other

D. Garbage collection will cause a runtime error due to the cycle

Solution

1. Step 1: Understand reachability in garbage collection

   Garbage collection frees objects unreachable from any external references, even if they reference each other.

2. Step 2: Apply this to cyclic references

   Since no external variables reference the cycle, the entire cycle is unreachable and will be collected.

3. Final Answer:

   The cycle of objects will be collected because they are unreachable from outside -> Option B

4. Quick Check:

   Unreachable cycles = collected [OK]

Hint: Unreachable cycles are collected despite internal references [OK]

Common Mistakes:

• Believing cycles prevent garbage collection
• Thinking only some objects in cycle are collected
• Expecting runtime errors from cycles