I don’t want to pile on but I have the exact same issue.
Dell 3650 MS Win Pro 64 23H2
My BC server version is 3.1.7
Live view on server is good to go.
Launching bluecherry_client with and without --mdk option produces the same.
Event Viewer gives me this
Faulting application name: bluecherry_client.exe, version: 3.0.0.0, time stamp: 0x6791c555
Faulting module name: flutter_windows.dll, version: 0.0.0.0, time stamp: 0x6781b757
Exception code: 0xc000041d
Other details. I have 425 cameras across multiple BC servers. I am at 3.1.7 on all. Server side has been super stable. Windows 11 Pro mostly running the 3.0.0 client. And I update that frequently. Live viewing on the BC server works.
What I noticed. I told my staff to use HLS on the client as the default streaming protocol.
After changing from RTSP to HLS yesterday, the bluecherry client exhibited the above problem. She locks up. I have to uninstall and reinstall, but even that doesn’t solve the problem. At the same time, I am adjusting primary and secondary stream URLs at the BC server and network cams. I am using a primary stream at various resolutions and 15 FPS but for viewing - 640x480 @ 15 and in some cases 480x320 maybe.
I will try to recreate the problem. I am in another building today away from the host I was sitting at yesterday. I will get back shortly today.
I think the switch from RTSP to HLS as the default streaming protocol in the client is where I am going wrong. I am going see if I can consistently reproduce the issue.
I have a Dell 3650 workstation i7 and 16MB RAM Intel UHD Graphics 750. Windows 11 Pro 23H2
BC Client is 3.0.0.beta22 running as a standard user.
BC server is running 3.1.7 16 Pelco cams CPU 19% Mem 17%
BC client…
I added all 16 cams from BC server A and rtsp streaming. client CPU 17% MEM 49%
All 16 cam secondary streams are 480x352@15FPS
I will let it run for 30 minutes viewing all 16 cams on one view no cycle.
logs.txt is not that exciting.
[2025-01-30T09:00:04.863554] App working directory: C:\Users___\AppData\Roaming\com.bluecherry\Bluecherry Client
[2025-01-30T09:00:05.197543] Running on UnityVideoPlayerMediaKitInterface video playback
Ok let’s crash this app. I am going change my default protocol to HLS.
I restarted the client. And Bingo! All cams appear stuck loading. client CPU 1% MEM 38%
I have use Task Manager to stop the client. And it stops at the same spot each time.
I thought I read HLS was better…
More info. I have these records (files) in the BC client working directory.
[2025-01-30T09:01:08.339674] v | cplayer: Set property: hwdec=“auto” → 1
[2025-01-30T09:01:08.360114] v | libmpv_render: GL_VENDOR='Google Inc. (Intel)‘l(R) UHD Graphics 750 Direct3D11 vs_5_0 ps_5_0, D3D11-32.0.101.5768)’
[2025-01-30T09:01:08.360114] v | libmpv_render: GL_SHADING_LANGUAGE_VERSION=‘OpenGL ES GLSL ES 3.00 (ANGLE 2.1.18844 git hash: 2693b03eba82)’
[2025-01-30T09:01:08.362541] v | libmpv_render: Loading hwdec driver ‘d3d11-egl’
[2025-01-30T09:01:08.361537] v | libmpv_render: GL_*_swap_control extension missing.er_query.at.ce…
[2025-01-30T09:01:08.379261] v | libmpv_render: Loading hwdec driver ‘d3d11va’ookie: bluecherrydvr=bq9lmap17ac7o7785173cbppj0; path=/“] → 1
[2025-01-30T09:01:08.443650] v | lavf: Could not set AVOption headers='cookie: bluecherrydvr=bq9lmap17ac7o7785173cbppj0; path=/
[2025-01-30T09:01:08.443650] v | lavf: ’
[2025-01-30T09:01:08.443650] v | lavf: Could not set AVOption seg_max_retry=‘5’s=‘ALL’
[2025-01-30T09:01:12.871118] v | cplayer: Set property: vid=“auto” → 111
[2025-01-30T09:01:12.887927] v | libmpv_render: GL_VENDOR=‘Google Inc. (Intel)‘GLE 2.1.18844 git hash: 2693b03eba82)’
[2025-01-30T09:01:12.890850] v | libmpv_render: Loading failed.ol extension missing.ES GLSL ES 3.00 (ANGLE 2.1.18844 git hash: 2693b03eba82)’.5768)’
[2025-01-30T09:01:12.901595] error | libmpv_render/dxva2-egl: Failed to create EGL surface
[2025-01-30T09:01:12.906531] v | libmpv_render: Loading failed.river 'd3d11va’imeout…15.6:7002/live/1lmap17ac7o7785173cbppj0; path=/”] → 1
[2025-01-30T09:01:12.976889] v | lavf: Could not set AVOption tls_verify=‘0’
[2025-01-30T09:01:12.977977] v | lavf: ‘ould not set AVOption headers=‘cookie: bluecherrydvr=bq9lmap17ac7o7785173cbppj0; path=/
[2025-01-30T09:01:15.496487] v | lavf: avformat_find_stream_info() finished after 0 bytes.
[2025-01-30T09:01:15.801069] v | demux: Stream is not seekable.tsp (libavformat)
[2025-01-30T09:01:15.812638] v | vf: [userdeint] 480x352 nv12 bt.601/bt.601-625/bt.1886/full/display SP=1.000000 CL=mpeg2/4/h264 crop=480x352+0+0
[2025-01-30T09:01:15.813698] v | vf: [userdeint] (disabled)
[2025-01-30T09:01:15.819344] v | libmpv_render: Video scale: 1.000000/1.000000
[2025-01-30T09:01:15.819344] v | libmpv_render: Texture for plane 0: 480x352ownt.1886/full/display SP=1.000000 CL=mpeg2/4/h264 crop=480x352+0+0
[2025-01-30T09:01:15.814828] v | vf: [autorotate] (disabled)y: (0, 0) 480x352 → (0, 0) 480x352mode.display SP=1.000000 CL=mpeg2/4/h264 crop=480x352+0+0
[2025-01-30T09:02:19.199189] v | vo/libmpv: mpv_render_context_render() not being called or stuck.
[2025-01-30T09:02:29.403036] v | vo/libmpv: mpv_render_context_render() not being called or stuck.
[2025-01-30T09:11:15.297662] v | cplayer: Set property: volume=0.000000 → 1
[2025-01-30T09:16:58.882885] v | cplayer: Set property: volume=0.000000 → 1
[2025-01-30T09:31:20.339626] v | cplayer: Set property: volume=0.000000 → 1
[2025-01-30T09:31:35.599354] v | cplayer: Set property: volume=0.000000 → 1
[2025-01-30T09:31:55.622806] v | cplayer: Set property: vid=“auto” → 111
[2025-01-30T09:31:55.643508] v | libmpv_render: Detected GLES 3.0. ES 3.0.0 (ANGLE 2.1.18844 git hash: 2693b03eba82)’
[2025-01-30T09:31:55.646044] v | libmpv_render: Loading failed.t rgba16f.exture_norm16.lf_float.ode. Direct3D11 vs_5_0 ps_5_0, D3D11-32.0.101.5768)’
[2025-01-30T09:31:55.658434] error | libmpv_render/dxva2-egl: Failed to create EGL surface
[2025-01-30T09:31:55.664815] v | cplayer: Set property: insecure=“yes” → -3bols’erop’
I removed the Client and reinstalled as the same user, added my BC server A and RTSP as default and the client locks up in the same manner after closing client and reopening.
More info… I am thinking the switch to HLS from RTSP causes this crash. No problem, you switch back to RTSP. However, the client crashes before one can get the far.
So uninstall app. Make sure files in \users\username\appdata\roaming\com.bluecherry <
Are removed. Reinstall. Same problem.
Using a standard user and elevating to an admin level user to install the Client. Same problem. Crash. Then log in as the admin level user. Clear files in …\appdate\Roaming\com.bluecherry Client starts up fresh!!! I am running 40 cams off 3 BC servers in cycle mode. No problems. Windows is stable. 32%CPU and 55% MEM
Cycle works @ 10s.
Additional info.
My local police station has 5 of my Dell 3650’s They can look into our buildings. They were having the same freeze problem on 3.0.0beta22 but went back to beta18 pm Win 11 and things are running well. I am going to try that myself.
Thanks,
Tom
Thanks for all the provided information. I tested on @brett.gamlin server and the problem seems to be the HLS streams as well.
HLS is only recommended on the WEB platform. RTSP is faster and more secure and it is recommended for the other platforms (Android, iOS, macOS, Windows and Linux) due to its lower latency and better compatibility with native mobile and desktop video players. Please, make sure to use RTSP instead of HLS if you’re able to access the settings.
I am aware that it is hard to get to the Settings page before the app crashes. I am investigating why appdata\Roaming\com.bluecherry is not being deleted on uninstall.
The problem is not limited to HLS. It also happens if the client’s protocol is set to RTSP.
I just deleted the com.bluecherry directory in APPDATA and re-configured my client from scratch.
I added back only the one server which you have been testing (which has 16 cameras defined).
The server settings default to RTSP (not HLS) anyway.
I then added one camera at a time to the view screen, checked that it worked and then closed and then reopened the client. It worked fine up until 8 cameras. When I added the 9th camera, it displayed fine on the view screen when I added it, but when I closed and reopend the client, the entire client immediately hung and needed to be killed by task manager.
it doesn’t seem to matter which camera is the 9th one added. It gets the same result. I also noticed that the task manager window sometimes shows “Efficiency mode” against bluecherry processes.
@brett.gamlin What happens when you press the “Add all to view” button? Does it crash as well? It may be failing to load all video player instances at once.
I downloaded the lastest bleeding edge windows client.
I uninstalled the previous client from my PC, deleted the com.bluecherry folder from the Appdata\Roaming folder in my profile, and then installed the bleeding edge version and reconfigured it from scratch.
Although it initially looked like the problem still existed, as the display still went unresponsive during the loading of the cameras for a minute or so, it did come good and is now behaving normally.
One minor point comes to mind though - would it be possible to include a build number or build date in the version information string displayed in the “Updates, Help and Privacy” tab of the client? Currently it is not possible to distinguish which version is installed on a PC as the version information displayed for the actual 3.0.0-beta22 version is the same as the version information displayed for the 3.0.0-beta22 bleeding edge version.
Looks like I was a bit too quick with the previous reply. I dont think the problem is entirely resolved yet.
The bleeding edge client is still hanging intermittently, such as when changing the layout mode for example between multiple and compact or vice versa, but this is not happening everytime.
When it does however, it still needs to be killed by task manager, but then seems to work again after a restart of the client application.
The hang is directly related to your hardware. In my machine, I can load up to 12 cameras without having any issues (AMD RYZEN 5, 20GB RAM, Integrated GPU). How many cameras are you displaying?
Can you try opening the client with the --mdk flag?
I was able to achieve a much better performance with MDK, with no crashes. With the default renderer (mpv), the app crashed with the same amount of cameras after a minute. MDK is already the default renderer for MacOS and Linux. We are investigating the possibility of making it the default renderer for Windows as well. Your feedback is really important.
I am testing the V3 client against several of my bluecherry servers. For this test I am opening 17 cameras from one of those servers. Most of our 10 or servers have around 16 cameras each.
I doubt it is the hardware. I am testing this on a PC with an intel i9 (24 cores) processor, 32GB RAM and NVIDIA T400 graphics adapter.
The --mdk option does appear to have resolved the hanging issue, but it is having problems rendering video from two older cameras.
Without the --mdk option, the bluecherry client will display all cameras but will hang when you first add all the cameras to the view. However, after killing the client with task manager, the client will restart and display all cameras normally without hanging again (unless you try to change view settings too much and then it hangs). The following two screen dumps show the hung view, and then the same view after the client is killed and restarted.
With the --mdk option, the bluecherry client has not hung on me at all yet. However it is failing to display video from two older analogue cameras which are connected though AXIS P7304 video encoders. They get displayed, first as LATE and then as TIMED OUT. The following screen dump shows the two timeouts on the two older cameras.
It is good to hear that the issue is no longer present when using MDK. We will work on making it the default video backend.
Regarding the two older cameras, to help us identify any errors or issues with the video streams, could you please send us the log files from their streams? You can find those in the log folder (Settings > Advanced Settings). Specifically, please send the files pertaining to the cameras experiencing the issue. If those logs are not sufficient, we may need access to your server to verify the issue directly.
I update NVR’s to 3.1.9
The Windows Client 18 to 22 and Bleeding edge are giving me the same result. What looks like the frames not being rendered. LIVE view works for all my cameras.
Any ideas?