Frontmatter
| id | 8803 |
| title | Suppress Neo.isDestroyed errors in RemoteMethodAccess |
| state | Closed |
| labels | enhancementaicore |
| assignees | tobiu |
| createdAt | Jan 19, 2026, 11:52 AM |
| updatedAt | Jan 19, 2026, 11:54 AM |
| githubUrl | https://github.com/neomjs/neo/issues/8803 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| contentTrust | |
| projected | |
| quarantined | 0 |
| signals | [] |
| blockedBy | [] |
| blocking | [] |
| closedAt | Jan 19, 2026, 11:54 AM |
Suppress Neo.isDestroyed errors in RemoteMethodAccess

tobiu
Jan 19, 2026, 11:54 AM
Input from Gemini 3 Pro:
✦ I have updated
src/worker/mixin/RemoteMethodAccess.mjsto suppressconsole.errorlogs when a remote method failure is caused byNeo.isDestroyed. This ensures cleaner logs during component destruction sequences.
Update
src/worker/mixin/RemoteMethodAccess.mjsto suppressconsole.errorlogging when a remote method fails due toNeo.isDestroyed.This ensures that correctly handled destruction sequences (using
traportimeout) do not pollute the console with false positives when they occur across thread boundaries (or within the remote dispatch logic).Action:
onRemoteMethodto checkif (err !== Neo.isDestroyed)before logging.