ZoneMinder 1.36.33 - Montage Review problem

[a_jurcak]

Hello,
I have such a problem with Montage Review. When I click on it and put the "History" tab, it says "No data found in range - choose differently". Eight cameras out of eleven are set to Modect, so there should be records in the history, but there aren't.
Next is the "All Events" tab, which when I open it, the window shows me HTTP error 500.
The tab "1 Hour" tells me the same thing as "History", i.e. "No data found in range - choose differently".
And finally the "8 Hour" tab which shows me an empty white window.
Does anyone know what to do with it please?
Thank you very much in advance for your reply.

[sqwish]

I have an issue with Montage Review as well. Very repeatable with both 1.36.32 and .33

• Click "Montage Review" Tab
• Click "History" button
• Use date-picker calendar widget to select start date of (arbitrary) 4/1/2023
• Try to use second calendar widget to select end-date, but won't change month and worse, gives HTTP 500 Internal Server Error
• Or just use this link to repeat the issue every time:

  Code: Select all

  https://mySERVER/zm/index.php?view=montagereview&fit=1&minTime=2023-04-01%2000:00:00&maxTime=2023-07-17%2011:04:43-04:00&live=0&scale=1&speed=1
  

• When I edited /etc/php/8.1/apache2/php.ini to set "memory_limit = 2048M" (formerly 128M), now instead of HTTP 500, I get "504 Gateway Time-out: The server didn't respond in time." (probably due to my proxy/gateway settings, but that's irrelevant because I still see out-of-memory issues like the below in /var/log/apache2/error.log:

Code: Select all

error.log.1:[Sun Jul 16 21:18:16.251486 2023] [php:error] [pid 1764] [client 10.1.1.101:36903] PHP Fatal error:  Allowed memory size of 2147483648 bytes exhausted (tried to allocate 20480 bytes) in /usr/share/zoneminder/www/skins/classic/views/js/montagereview.js.php on line 87, referer: https://mySERVER/zm/?view=montagereview&filtering=&MonitorName=&Source=&minTime=2023-07-16+20%3A04%3A28-04%3A00&maxTime=2023-07-16+21%3A04%3A28-04%3A00&fit=1&live=0

... which tells me it would have run out of memory anyway, even if it hadn't timed out. My gut feeling is that if the screen code limited the date range for history to ... 3days? 7days? (max) then it would solve this problem.

@iconnor? iconnor@ #iconnor

[iconnor]

I have a bunch of code to merge that loads all the frame data in chunks. There is just too much of it. When I'll get to that I don't know.

[sqwish]

Thanks for the reply. If I had more free time, I'd offer to help merge that code. In the meantime, if anyone else has this problem: You can edit the URL's date ranges to limit it to around 1 day at a time (or probably more, I didn't experiment) and it'll load the video history just fine.

I almost want to just rip out the "End date" calendar widget and have the code assume it's a 24-hr window from the start date. We'll see how much free time I have