Chrome Version : 48.0.2564.109 m on Windows 7
We have a Chrome Extension developed for our project.
The extension within it has a video element the source of which is the stream selected from the "chrome.desktopCapture.chooseDesktopMedia". The image for every 500ms is captured as webp from the video played and sent back to the host application via long lived connections.
What we notice is that this extension is crashing after a brief usage in time (sometimes at 5mins sometimes at 30mins). Profiling the extension we see the Heap memory constant at ~2.6MB throughout until the extension getting crashed.
One odd behavior that we noticed is that clicking the "Collect Garbage" button in the Timeline tab of the Developers tool for the extension is helping the extension to run for longer period without getting crashed.
Questions :
1. Is there any existing issue with Google Chrome browser extension's garbage collection not getting triggered until it is manually started ?
2. By any means is it possible to kick start this garbage collection process from the extension's
Related
I am building a jukebox-like javascript application that runs in the browser. This application will run on a dedicated machine in an exhibition.
It will have to run continuously for 8 hours. At certain moments it will navigate to a different page (or reload current page with different search parameters).
It needs to play audio on all pages. But audio in the browser can only play user-initiated. Is there a way to bypass the user-initiation requirement in chrome or safari? Again, this will be a dedicated machine, so browser flags etc are an option.
If this is not possible in chrome or safari, what would be another solution/environment that can do this?
Your are in total control of the running browser (because you start the kiosk). So you can start the browser without the usual security behavior that prevent auto play.
For example if you are using Google chrome you can start it with chrome.exe --autoplay-policy=no-user-gesture-required
So i use this extension to record my online classes using a remote desktop .
it works perfect but when i stop my connection to the remote computer the recording stops.
i saw this post
In this post the answer says to use the Chrome extension source viewer
i tried it but i couldn't wrap my head around the code.
one thing i found is that the extension sends a runtime message called "RECORDING_STOPPED" when recording ends and when i disconnect my remote desktop connection it apparently sends it that time also
i checked the /static/js/main.c502a7e6.js file Line : 16 , Column : 4875 as the line is quite long i didn't understand it
TLDR; How do I enable the autoplay-policy flag in >= Chrome 62? The autoplay problem has been thoroughly discussed, but in this question I want to edit the settings for my own browser to run a browser extension game that can play its own sounds in a "kiosk".
Issue; I am building a chrome extension that plays a game on top of web pages. I am now creating the demo mode that automatically goes to new urls and launches the game so viewers can watch it in galleries, etc. However, because this is an automated script (users watch it passively) and these web pages are random (so do not have a high Media Engagement Index (MEI) chrome://media-engagement/) my extension sounds are suspended chrome://media-internals/:
I have looked at:
Javascript but their policy says a user has to interact with the domain (which is not possible)
Increasing the domain's MEI score (again, not possible)
Setting the "Developer Switch" at chrome://flags/#autoplay-policy to allow autoplay (but it seems this page no longer works as of at least Chrome 76).
Picture of game for context:
I temporarily "solved" this by using Chrome Canary v78 with start up flags found in this SO question description. In Terminal (Mac)...
/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --autoplay-policy=no-user-gesture-required
I am running a test in Firefox that requires me to open thousands of websites (one at a time) and close their tabs. I am having a weird memory leak issue that consumes all my virtual memory after a few hours and causes the test to crash. I am thinking that this may be occurring because Firefox stores in its history every site that was visited and other relevant information. When I close the test and reopen the browser, the history is cleared (but not while the test is running).
Is there any way I can use javascript to have Firefox stop storing the browser history?
I'm wondering if anyone has run into new problems with using the HTML5 application cache in Mobile Safari on iOS 5 devices? I had previously written an offline web app that worked well in iOS 4, but as devices that use this app are being moved over to iOS 5, I am discovering problems when devices are offline and attempting to access what should be cached resources.
I can confirm that the application caching procedure is working as expected, as I can track the hits to my webserver as resources are downloaded while the device is online.
The problem manifests itself in the form of the "Cannot Open Page: Safari cannot open the page because it is not connected to the Internet" dialog box when I attempt to follow a link to a page that should be cached while I am offline.
Interestingly, around the same time this error pops up, in the Debug Console one also gets the "JavaScript execution exceeded timeout" error, similar to what is mentioned in this thread. I'm not doing any computation nearly as complicated as what was posted there, but the suggestion to kill and restart Safari seems to fix both problems, at least for now.
So maybe this question is less a request for help and more of a landing place for future searchers to share their experiences.
Please check if you have added the cached page itself into the manifest file, in below example they are HTMLPage1.htm & HTMLPage2.htm. I have the same problem but it works after adding the cached page link.
CACHE MANIFEST
CACHE:
images/cover.png
HTMLPage1.htm
HTMLPage2.htm
NETWORK:
*