[Bug]: Cider stops responding after a while

[Micka-DAOUD]

Describe the Bug

Every time I launch Cider, it freezes and stops working after a while (from 10 seconds to 1 min, the time before the crash seems to be quite random) and displays this prompt:

Steps to Reproduce

• Open Cider
• Wait for the app to crash

Environment Information

• OS: Fedora Linux 36 (Xfce)
• Desktop Environment: GNOME 42.4
• App Version: 1.5.9
• Commit ID:

How did you download the software?

Flathub

Anything else?

• The bug started happening right after I changed my desktop environment from Xfce to GNOME
• Tried uninstalling then reinstalling the app, but nothing changed
• Also tried to install via Snap package but nothing changed

Code of Conduct

• I agree to follow this Cider's Code of Conduct

Disclaimer

• I acknowledge the Support Disclaimer

[btyu]

Same on Windows. It has happened many times, and is indeed a serious bug. Whether reloading or not doesn't help.

[coredev-uk]

Try launching cider through the terminal, post a picture of the log please.

Have you tried a clean install?

[BrunoBernardino]

I've also been running into this for the last 3 weeks or so (after some update, can't tell if it was 1.5.9 or earlier). It's quite random, and starting the app from the terminal doesn't seem to help.

I'm on Linux Mint, Cinnamon. Cider was installed via Flathub and I've had it for many months without any problem before, on this same setup.

Here's the terminal full output (note the window goes blank and music stops playing before I CTRL+C, and when I do, the output is probably expected for that command). It doesn't seem like anything is logged when the window stops responding.

$ cider
[11:04:17.203] [info]  [AppEvents] App started
[11:04:17.329] [info]  [PluginHandler] Loaded plugins: [
  'chromecast.js',
  'discordrpc.js',
  'lastfm.js',
  'menubar.js',
  'mpris.js',
  'playbackNotifications.js',
  'raop.js',
  'thumbar.js',
  'webNowPlaying.js'
]
[11:04:17.430] [info]  [AppEvents] App ready
[11:04:17.431] [info]  [Cider] Application is Ready. Creating Window.
[11:04:17.446] [info]  Setting up handlers for local files
[11:04:17.457] [info]  [Connect] Auth URL: https://connect.cidercollective.dev/callback/discord?app=cider&appPort=9000
[11:04:17.484] [info]  WebSocketServer started on port: 26369
[11:04:17.493] [info]  [Cider][Widevine] Status: {
  oimompecagnajdejgnnjijobebaeigek: {
    name: 'Widevine Content Decryption Module',
    status: 'new',
    version: '4.10.2557.0'
  }
}
[11:04:17.541] [info]  {
  auxAttributes: {
    amdSwitchable: false,
    canSupportThreadedTextureMailbox: false,
    glResetNotificationStrategy: 0,
    inProcessGpu: true,
    initializationTime: 0,
    isAsan: false,
    jpegDecodeAcceleratorSupported: false,
    optimus: true,
    passthroughCmdDecoder: false,
    sandboxed: false,
    softwareRendering: false,
    subpixelFontRendering: true,
    visibilityCallbackCallCount: 0
  },
  gpuDevice: [
    {
      active: true,
      cudaComputeCapabilityMajor: 0,
      deviceId: 9632,
      gpuPreference: 0,
      vendorId: 4318
    },
    {
      active: false,
      cudaComputeCapabilityMajor: 0,
      deviceId: 18086,
      gpuPreference: 0,
      vendorId: 32902
    }
  ]
}
[11:04:17.543] [info]  From here can you check for real changes, the initial scan has been completed.
[11:04:17.543] [info]  Cider client port: 9000
[11:04:17.546] [info]  Cider remote port: 6942
[11:04:17.549] [info]  remote broadcasted
^C[11:08:30.531] [warn]  Cider exited.
[11:08:30.532] [error] Error sending from webFrameMain:  Error: Render frame was disposed before WebFrameMain could be accessed
    at EventEmitter.s._sendInternal (node:electron/js2c/browser_init:173:843)
    at EventEmitter.g._sendInternal (node:electron/js2c/browser_init:169:2235)
    at node:electron/js2c/browser_init:201:729
    at new Promise (<anonymous>)
    at Object.invokeInWebContents (node:electron/js2c/browser_init:201:477)
    at EventEmitter.g.executeJavaScript (node:electron/js2c/browser_init:169:3097)

[BrunoBernardino]

I can confirm in my situation it seems to have been caused by a particular command that killed all node processes, and ever since avoiding that command, particularly, Cider's been working fine.