Javascript TypeError

[NhKPaNdA]

Type of installation

Portable (.zip)

Version

Stable

Type of reader (if reader related)

image

Steps to reproduce

Unknown

✔️ Expected Behavior

No error

❌ Actual Behavior

Until I closed this specific instance of yomikiru, this error would continue to pop up after an amount of time. There were 2 of them since I had 2 instances open at the same time. The error didn't reappear until I closed both instances.

[mienaiyami]

Did it appear after certain time? Do you have estimate of when it appeared since opening the app.

[NhKPaNdA]

No idea since I tend to leave the app open until I finish reading the title or restart my pc which could be days in between. I just remember it kept reappearing at set intervals until I closed said instances.

[mienaiyami]

Couldn't reproduce it, maybe fixed in latest version. If you still encounter this, please let me know. Keeping this issue open for a month just in case.

[NhKPaNdA]

I thought this was finally solved since I tried to reproduce it with multiple instances open for extended periods of time but it never reoccurred. So I gave up until now when I had 2 instances open, one with a manga loaded (less than 4 hours open) and one just sitting at the home page (unsure but not more than a day or 2 staying open), and after closing the home page instance the error reappeared. This is the following error it tried to fill out a new issue for so I'll post it here instead.

App Version: 2.22.5
Platform: win32 x64
OS Version: 10.0.19045

Error Details

{
  "appVersion": "2.22.5",
  "systemInfo": {
    "appVersion": "2.22.5",
    "platform": "win32",
    "arch": "x64",
    "osVersion": "10.0.19045",
    "nodeVersion": "v16.17.1",
    "electronVersion": "22.3.25",
    "totalMemory": 67769704448,
    "freeMemory": 46260781056,
    "cpuCount": 16
  },
  "timestamp": "2025-11-13T15:34:40.946Z",
  "errors": [
    {
      "message": "Object has been destroyed",
      "stack": "TypeError: Object has been destroyed\n    at Timeout.t [as _onTimeout] (D:\\[Yomikiru]\\resources\\app.asar\\.webpack\\main\\index.js:2:301546)\n    at listOnTimeout (node:internal/timers:559:17)\n    at process.processTimers (node:internal/timers:502:7)",
      "severity": "critical",
      "context": {
        "source": "uncaughtException"
      },
      "timestamp": "2025-11-13T15:34:15.884Z",
      "handled": false
    }
  ]
}

[NhKPaNdA]

So I had this occur again but this time there was only 1 instance of the app open and it was on the home page. I didn't close anything it was just sitting there minimized for not longer than an hour and the error reappeared. The only thing that was most active on my PC at the time was my VPN disconnecting and reconnecting again and again till it failed and blocked all internet traffic.

[NhKPaNdA]

Got the error again basically with the same process as my previous message (single app instance open at the home page minimized and not touched for a while and vpn connecting in the background) on the new version but the error looks like it hasn't changed at all after the update.

{
  "appVersion": "2.23.0",
  "systemInfo": {
    "appVersion": "2.23.0",
    "platform": "win32",
    "arch": "x64",
    "osVersion": "10.0.19045",
    "nodeVersion": "v16.17.1",
    "electronVersion": "22.3.25",
    "totalMemory": 67769704448,
    "freeMemory": 37649649664,
    "cpuCount": 16
  },
  "timestamp": "2025-11-30T16:27:15.161Z",
  "errors": [
    {
      "message": "Object has been destroyed",
      "stack": "TypeError: Object has been destroyed\n    at Timeout.check [as _onTimeout] (D:\\[Yomikiru]\\resources\\app.asar\\.webpack\\main\\index.js:17647:51)\n    at listOnTimeout (node:internal/timers:559:17)\n    at process.processTimers (node:internal/timers:502:7)",
      "severity": "critical",
      "context": {
        "source": "uncaughtException"
      },
      "timestamp": "2025-11-30T16:26:58.454Z",
      "handled": false
    }
  ]
}