What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	8961
title	Fix: Memory Leak in Neo.component.Canvas due to missing destroy()
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 3, 2026, 2:01 PM
updatedAt	Feb 3, 2026, 2:12 PM
githubUrl	https://github.com/neomjs/neo/issues/8961
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 3, 2026, 2:12 PM

Fix: Memory Leak in Neo.component.Canvas due to missing destroy()

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v12.0.0 bugai

tobiu commented on Feb 3, 2026, 2:01 PM

Neo.component.Canvas is missing a destroy() method. While it correctly registers the canvas with the worker on mount, it fails to unregister it on destruction.

Consequence: The Canvas Worker retains OffscreenCanvas contexts, render loops, and data structures indefinitely, leading to a memory leak and potential GPU process crash over time as views are created and destroyed.

Task:

Implement destroy() in src/component/Canvas.mjs.
Send a destroyCanvas (or similar unregister) message to the Canvas Worker.
Implement the corresponding destroyCanvas handler in src/worker/Canvas.mjs (and specifically in src/canvas/Sparkline.mjs if it maintains its own map) to clean up the internal state and stop render loops.

tobiu added the bug label on Feb 3, 2026, 2:01 PM

tobiu added the ai label on Feb 3, 2026, 2:01 PM

tobiu added parent issue #8930 on Feb 3, 2026, 2:01 PM

tobiu referenced in commit 05a855c - "Fix: Memory Leak in Neo.component.Canvas due to missing destroy() (#8961)" on Feb 3, 2026, 2:10 PM

tobiu Feb 3, 2026, 2:10 PM

Input from Gemini 3 Pro:

✦ I have fixed the memory leak in Neo.component.Canvas and Neo.component.Sparkline.

Changes:

src/worker/Canvas.mjs: Added unregisterCanvas to remove canvas references from the worker's internal map.

src/component/Canvas.mjs:

Implemented destroy() to call unregisterCanvas if the canvas was registered.

Updated afterSetMounted() to call unregisterCanvas when the component is unmounted (value === false).

src/canvas/Sparkline.mjs:

Added unregister remote method to cleanup the renderer's specific state (active render loops, item maps).

src/component/Sparkline.mjs:

Implemented destroy() to call renderer.unregister.

Updated afterSetMounted() to call renderer.unregister on unmount.

Outcome: OffscreenCanvas contexts and worker-side render loops are now properly cleaned up when a component is destroyed or unmounted (e.g., via removeDom: true). This prevents memory leaks and ensures long-term stability.

tobiu assigned to @tobiu on Feb 3, 2026, 2:11 PM

tobiu closed this issue on Feb 3, 2026, 2:12 PM