ZoneMinder Forums

Maybe one needs slow channel, say 2-3 Mpbs, to reproduce it, I'm not sure.

And maybe this video will clarify the problem

I've found out that it happens only when B/W settings are Low or Medium. When I set B/W to High, the bug is gone.

1.37.65~20241031 (focal) - problem persists

iconnor wrote: ↑Wed Oct 23, 2024 10:38 pm Actually the scale dropdown doesn't seem to be doing anything here at the moment. I'll dig in.

It does scale the video. But not only frame size )
I have time with seconds on camera OSD so I can tell

Hello. In MJPEG mode scaling image size in event view scales playback speed reciprocally (with linear scale factor squared). For example, camera (and recording) original resolution is 2560x1440, when I set scale to "Max 1280", which is linear 1/2, my actual playback speed goes ~4x and I need to set ...

I noticed that there's a new build 1.37.63~20240723103852 pushed to Ubuntu repo
Did anyone try it already, what about those segfaults, still there?

I have had a drive fail. Several of my monitors were pointed at a storage path on that dead drive. Now of course, ZM wont start. How can I edit the monitors to point them to a working storage without ZM running? Just manually update Monitors table in mysql database 'zm' accordingly. You'll need to ...

The relevant package is no longer in noble. Only jammy, and it complains loudly of tons of broken dependencies when it's tried to be forced. https://ppa.launchpadcontent.net/iconnor/zoneminder-master/ubuntu/dists/noble/main/binary-amd64/ You may look here, debs for last 8 builds are available https ...

Same experience, had to revert to 1.37.63~20240715.8-focal amd64

All zmc processes were almost instantly and constantly crashing with segfaults on 1.37.63~20240719144459-focal amd64

Did you restart zm? zmc processes don't pick up logging changes automatically. when I do systemctl restart it restarts the whole CG (cgroup), so yes. I didn't restart the apache part though UPD: Just upgraded to yet another new build (1.37.63~20240716103948-focal) on another machine, new strange ...

in Database Log , but not in file log, while both are set to Level = WAR: ERR Got unexpected memory map file size 37330480, expected 37330472 zm_monitor.cpp 1036 This must be a bug, because when I set LOG_LEVEL_DATABASE=None, stop ZM, truncate zm.Logs table and restart ZM, I'm still getting them ...

Please take note of ram usage. I believe once we get the crashing fixed, it will use significantly less ram when recording. At least that is the hope I'm monitoring it and yes, I can say it's more efficient now. Especially when I explicitly specify MaxImageBufferCount. Also, segfaults are rare now ...

iconnor wrote: ↑Sat Jul 13, 2024 2:04 pm I may have found the problem. Certainly found and fixed A problem.
Packages building.

Great!
Meanwhile, just FYI: downgrading to latest 37.59 (1.37.59~20240508.78-focal) did the trick for me.

There are some signficant changes between 1.37.60 and 1.37.62 regarding how/when we can free up the ram in packets. ........... The problem is exacerbated by the backtraces being almost useless these days. Thanks for the feedback! Will downgrading to 1.37.59 or even (.57) work as a temporary ...

Another thing that might be important: It all started after I did apt-get full-upgrade on this system 2 days ago, which also upgraded ZM. To get rid of these errors I downgraded ZM consequently to: 1.37.61~20240705153736-focal 1.37.61~20240703085514-focal 1.37.61~20240628094110-focal But neither ...

INF is not useful. Need Debug=4 Hi. Ubuntu Server 5.15.0-113-generic #123~20.04.1-Ubuntu. zoneminder-dbg/focal,now 1.37.62~20240707094607-focal amd64 [installed] zoneminder-doc/focal,now 1.37.62~20240707094607-focal all [installed,automatic] zoneminder/focal,now 1.37.62~20240707094607-focal amd64 ...