Comments (5)
In montage.js there is code in "window.onbeforeunload = function(e) {" that stops the monitors.
Why is this code not used?
Were there any problems?
I realized there is a problem with the confirmation pop-up window.
from zoneminder.
Why not leave the function like this: ?
window.onbeforeunload = function(e) {
console.log('unload');
//event.preventDefault();
for (let i = 0, length = monitorData.length; i < length; i++) {
monitors[i].kill();
}
};
from zoneminder.
Or here's a more correct code:
document.onvisibilitychange = () => {
if (document.visibilityState === "hidden") {
for (let i = 0, length = monitorData.length; i < length; i++) {
monitors[i].kill();
}
}
};
from zoneminder.
It is code that I was trying out. When the browser is overloaded, trying to navigate away takes forever. So this function is supposed to stop the streams so that the browser can actually get around to navigating away.
from zoneminder.
I highly doubt that any message from videostore has anything to do with navigating away from the montage view. Normally those messages are caused by changes in timestamps back in time, although our current code should not allow that.
from zoneminder.
Related Issues (20)
- The placement of monitors on the Montage page is broken again HOT 6
- Todo: pause status updates if status is hidden on montage
- Todo: We need to not even try to load cameras that are off view. HOT 4
- Rate=1 on Watch page does not work HOT 4
- Todo: Requires preventing server CPU overload HOT 5
- UI Improvement on watch view HOT 3
- Thoughts on event view layout HOT 4
- js error in watch HOT 1
- Replace the top menu with a side menu HOT 4
- Merge Montage & Montage Review page
- Error when trying to install on archlinux HOT 4
- "Path must be set to a valid value" returned when setting an ONVIF camera HOT 2
- "Monitors" Table Missing "WallClockTimestamps" Column HOT 2
- FreeBSD image missing in CI HOT 2
- ZM stops listening to ONVIF events if a camera becomes unavailable and then reappears on the network.
- Segmentation fault: 'zmc -m 1' exited abnormally, exit status 255 HOT 3
- When executing the CMD_PAUSE, CMD_SEEK, CMD_QUERY commands getCmdResponse stream error occurs: socket_sendto( /run/zm/zms-204049s.sock ) failed: Connection refused HOT 3
- Support for sending multiple "connkey" is required when executing commands such as CMD_QUERY, etc. in "zm_eventstream"
- Signature by key ABE4C7F993453843F0AEB8154D0BF748776FFB04 uses weak algorithm (rsa1024) HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zoneminder.