BC Client 3.0.0-beta21 hangs on startup

I have been running the BC client 3.0.0-beta21 for several weeks now on a windows 11 system and it’s been reasonably stable, so today I just added 15 new cameras to one of my BC servers. The cameras and server are working fine and the cameras can be viewed quite successfully from the server’s web liveview page.

After adding the new cameras to the server, I found I had to reboot the BC client application before it would see the new cameras. After restarting the client, I tried to add the new cameras to the client’s view page, but the client immediately hung and became completely unresponsive. None of the cameras displayed and I could not close the client, nor could I even move the client window on the desktop. I had to kill the client using task manager in order to close it.

Now, every time I start the client it immediately hangs as described above and I have to kill it with task manager.

An extract from the client log for one of the cameras that had been displaying fine in the client previously, shows:

[2025-01-10T14:00:07.066604] v | libmpv_render: GL_VENDOR=‘Google Inc. (NVIDIA)’
[2025-01-10T14:00:07.068603] v | libmpv_render: Loading hwdec driver ‘d3d11-egl’
[2025-01-10T14:00:07.067603] v | libmpv_render: Loaded extension GL_EXT_disjoint_timer_query.
[2025-01-10T14:00:07.068603] v | libmpv_render: Using FBO format rgba16f.
[2025-01-10T14:00:07.066604] v | libmpv_render: Detected GLES 3.0.
[2025-01-10T14:00:07.067603] v | libmpv_render: Loaded extension GL_KHR_debug.
[2025-01-10T14:00:07.068603] v | libmpv_render: Loading failed.
[2025-01-10T14:00:07.066604] v | libmpv_render: GL_VERSION=‘OpenGL ES 3.0.0 (ANGLE 2.1.18844 git hash: 2693b03eba82)’
[2025-01-10T14:00:07.067603] v | libmpv_render: Testing FBO format rgba16f
[2025-01-10T14:00:07.066604] v | libmpv_render: GL_RENDERER=‘ANGLE (NVIDIA, NVIDIA T400 4GB Direct3D11 vs_5_0 ps_5_0, D3D11-31.0.15.3770)’
[2025-01-10T14:00:07.067603] v | libmpv_render: Loaded extension GL_ANGLE_translated_shader_source.
[2025-01-10T14:00:07.069603] v | libmpv_render: Loading hwdec driver ‘dxva2-egl’
[2025-01-10T14:00:07.067603] v | libmpv_render: Loaded extension GL_EXT_color_buffer_half_float.
[2025-01-10T14:00:07.066604] v | libmpv_render: Loaded extension GL_EXT_texture_norm16.
[2025-01-10T14:00:07.066604] v | libmpv_render: GL_SHADING_LANGUAGE_VERSION=‘OpenGL ES GLSL ES 3.00 (ANGLE 2.1.18844 git hash: 2693b03eba82)’
[2025-01-10T14:00:07.067603] v | libmpv_render: GL_*_swap_control extension missing.
[2025-01-10T14:00:07.068603] v | libmpv_render: No advanced processing required. Enabling dumb mode.
[2025-01-10T14:00:07.177873] error | libmpv_render/dxva2-egl: Failed to create EGL surface
[2025-01-10T14:00:07.190414] v | libmpv_render: Loading failed.
[2025-01-10T14:00:07.191414] v | libmpv_render: Loading failed.
[2025-01-10T14:00:07.190414] v | libmpv_render: Loading hwdec driver ‘d3d11va’
[2025-01-10T14:00:07.190414] v | libmpv_render: Loading failed.
[2025-01-10T14:00:07.190414] v | libmpv_render: Loading failed.
[2025-01-10T14:00:07.191414] v | libmpv_render: Loading hwdec driver ‘dxva2-dxinterop’
[2025-01-10T14:00:07.191414] v | libmpv_render: Loading hwdec driver ‘cuda’
[2025-01-10T14:00:07.190414] v | libmpv_render: Loading hwdec driver ‘dxva2-dxgi’
[2025-01-10T14:00:07.210421] v | libmpv_render/cuda: cu->cuGLGetDevices(&device_count, &display_dev, 1, CU_GL_DEVICE_LIST_ALL) failed → CUDA_ERROR_OPERATING_SYSTEM: OS call failed or operation not supported on this OS
[2025-01-10T14:00:07.213413] v | cplayer: Set property: loop-playlist=“yes” → 1
[2025-01-10T14:00:07.212415] v | cplayer: Set property: loop-file=“no” → 1
[2025-01-10T14:00:07.212415] v | libmpv_render: Loading failed.
[2025-01-10T14:00:07.212415] v | cplayer: Set property: speed=1.000000 → 1
[2025-01-10T14:00:07.212415] v | cplayer: Set property: tls-verify=“no” → 1

Any suggestions on how to get past the initial hang of the client?

I don’t particularly want to rebuild the client configuration from scratch again if it can be helped.

Cheers.

If you open the Task Manager, is the app consuming the entire available memory, CPU or GPU? This can be the cause of the hang. Rendering videos is a consuming task, rendering multiple videos at the same time is even more consuming. The limits of your computer needs to be respected.

If that is not the case, can you send the logs of the app?

Additionally, see this pending optimization.

I am running the client on a windows 11 PC with 32GB RAM.

I does not appear to be a memory issue.

The performance tab shows the performance stats for the bluecherry client when it hangs as:

CPU: 0%
MEN: 123.0MB
Disk: 0 MB/s
Network: 0 Mbps
Status: Efficiency Mode

When the BC client starts, it immediately tries to display the view that I last set up which is a server with 16 cameras. The client hangs immediately and has only produced logs for 8 of the cameras. They are attached.

The thing is that I have a version 2 client that is set to view the same server and it can display all 16 cameras with no problems at all.

Despatch Office (mqn-vms-06.bundysugar.com.au).txt (6.0 KB)
Traffic Office (mqn-vms-06.bundysugar.com.au).txt (5.9 KB)
WH 3 (Pick & Pack) (mqn-vms-06.bundysugar.com.au).txt (5.8 KB)
WH 8 (mqn-vms-06.bundysugar.com.au).txt (5.7 KB)
WH 11 Inside Left (mqn-vms-06.bundysugar.com.au).txt (6.2 KB)
WH 11 Inside Right (mqn-vms-06.bundysugar.com.au).txt (5.7 KB)
WH11 A Trailer Left (mqn-vms-06.bundysugar.com.au).txt (4.3 KB)
WH11 A Trailer Right (mqn-vms-06.bundysugar.com.au).txt (1.2 KB)

Can you attach the logs.txt file? This is the file that contains crash information.

Also, what is the version of your Bluecherry Server?

I am running Bluecherry server 3.1.8 on Debian 12. It is a native installation on a server called mqn-vms-06.

Client log file is attached.

logs.txt (10.8 KB)

Thank you for providing your logs. While they appear normal, we need to do some further investigation to pinpoint the cause of the issue you’re experiencing.

To help us diagnose the problem, please follow these steps:

  1. Download and install the latest bleeding edge version of Bluecherry: You can find the installer here: Release bleeding_edge · bluecherrydvr/unity · GitHub
  2. Launch the application with the --mdk flag:
    • Locate the Bluecherry client executable. This is usually found in C:\Program Files (x86)\Bluecherry DVR.
    • Open a terminal or command prompt.
    • Navigate to the directory containing the executable.
    • Run the following command: ./bluecherry_client.exe --mdk

Please let us know if this resolves the issue.

What we’re checking:

We suspect the issue might be related to how the client interacts with your camera’s video stream. The --mdk flag switches the video rendering method to a different technology (MDK) that we use by default on Linux. This will help us determine if the problem lies with the default Windows rendering method (MPV).

If this doesn’t solve the problem, we may need to request temporary remote access to your server to conduct further investigation.

Thank you :slight_smile: