how to stop all tabs? "Offline mode" does not stop connection attempts
tell me who knows, how to stop all tabs? Even when I enable the "offline mode", tabs with heavy javascript continue trying to load, consuming CPU resources. I want they to stop immideately. I tried different extensions, but results are unsatisfactory. Does anybody know some trick? My goal is to find a method to flush all javascript structures in RAM. I explored about:memory, and tried the vmmap.exe (process memory analyzer) from the Sysinternals Suite, but I have not succeeded so far. Auto unload tab -- is not a solution. For example I clicked on links and opened 30 tabs in background. PC starts working very slow, Now I want to stop all them, and to read the loaded information (webpages). How to do it? I think it is the weakest side of Firefox. Needed to abrupt all attempts to make network connection, after the "offline mode" is enabled. I need something to stop javascript's attempts to connect, to calm it down. I want to start read webpages already loaded, and javascript occupies CPU. To kill threads in the Process Manager is not a way to do at all, Auto-unload also, I want to read those webpages. I have enough of RAM, it is not used more then a half. Many years ago, when there was HTML4, I used for a little the Maxton browser. It had a button to stop all pages. All similiar Firefox extensions do not act effectively like that. the issue not in scarcity of RAM, but in a badly design of browser's architecture, that javascript occupies users' PCs.
Όλες οι απαντήσεις (8)
You likely already tried these but just in case... Have you tried these two extensions?
https://addons.mozilla.org/en-US/firefox/addon/superstop/?src=search
and
https://addons.mozilla.org/en-US/firefox/addon/stop-all-button/?src=search
There's also this that might have some useful information
I'm researching this.
You want to kill all connections and prevent javascript from continually trying to load on all tabs at will, right?
Τροποποιήθηκε στις από το χρήστη Eve
Your post is not helpful. I came to conclusion that, such to say, user-level methods (extensions etc) do not work. It is needed some trick with virtual memory - to empty working set or something.
To flush all javascript structures from the memory heap, that only the loaded html must be displayed in tabs, without javascript ride on CPU.
I want not to stop auto-reload (auto-refresh) attemps, such webpages are rare, even when they try json requests, it isn't a problem. I mean to stop javascript to make any calculations on CPU after I enable the offline mode. As I wrote, it is a weak side of Firefox.
Τροποποιήθηκε στις από το χρήστη Niamh
disable javascript
in `about:config` disable `javascript.enabled`
You did not understand what I wrote. Javascript is necessary to display the webpages correctly. And it is needed to be halted aftewards, not to do any work in RAM. dom.always_stop_slow_scripts is not a solution either
Τροποποιήθηκε στις από το χρήστη Niamh
There is a non-zero chance that such settings, (perhaps), may help:
javascript.options.array_prototype_values
javascript.options.asmjs
javascript.options.asyncstack
javascript.options.baselinejit
javascript.options.compact_on_user_inactive
javascript.options.discardSystemSource
javascript.options.dump_stack_on_debuggee_would_run
javascript.options.gc_on_memory_pressure javascript.options.compact_on_user_inactive_delay
javascript.options.ion
javascript.options.ion.offthread_compilation
javascript.options.mem.gc_allocation_threshold_mb
javascript.options.mem.gc_compacting
javascript.options.mem.gc_dynamic_heap_growth
javascript.options.mem.gc_dynamic_mark_slice
javascript.options.mem.gc_generational
javascript.options.mem.gc_high_frequency_heap_growth_max
javascript.options.mem.gc_high_frequency_heap_growth_min
javascript.options.mem.gc_high_frequency_high_limit_mb
javascript.options.mem.gc_high_frequency_low_limit_mb
javascript.options.mem.gc_high_frequency_time_limit_ms
javascript.options.mem.gc_incremental
javascript.options.mem.gc_incremental_slice_ms
javascript.options.mem.gc_low_frequency_heap_growth
javascript.options.mem.gc_max_empty_chunk_count
javascript.options.mem.gc_min_empty_chunk_count
javascript.options.mem.gc_per_compartment
javascript.options.mem.gc_per_zone
javascript.options.mem.gc_refresh_frame_slices_enabled
javascript.options.mem.high_water_mark
javascript.options.mem.log
javascript.options.mem.max
javascript.options.mem.notify
javascript.options.native_regexp
javascript.options.parallel_parsing
javascript.options.shared_memory
javascript.options.showInConsole
javascript.options.strict
javascript.options.throw_on_asmjs_validation_failure
javascript.options.throw_on_debuggee_would_run
javascript.options.wasm
javascript.options.wasm_baselinejit
But in order to fine-tune them, it is necessary for user to have a master's degree in computer science.
Τροποποιήθηκε στις από το χρήστη Niamh
Hi Clayten,
While this may not be exactly what you're looking for, it's a different approach. Assuming that you're opening these new tabs in the background, the following add-on will prevent the content from loading until you actually click on the tab: https://addons.mozilla.org/firefox/addon/loadtabonselect/
NOTE: I haven't tried it myself.
I hope that helps.