Enhances Chaturbate by adding multiple new features.
< Feedback on Chaturbate Enhancer
Correction, the script crash also with the console open, it takes just longer.
Hi! That's interesting. Will look into this. Thank you for this report.
Please support Chaturbate Enhancer development - see how at https://cb-enh.improper.dev/contribute
Hello! For a few months now, when leaving Chaturbate transmissions in tabs, the memory increases until the system is left without ram. It is caused by this script.
It is very easy to replicate. You only have to open about 5 or 6 transmissions in tabs and after 20 or 30 minutes each tab consumes between 2 and 4 GB of memory. Reaching the point of crashing the browser.
I tried this and it happens in Chrome, Opera and Firefox with 32gb ram in system.
With only 1 transmission the same thing happens but it takes longer to block.
In Chromium browsers it blocks the tab with an out of memory message. When you reload the page it frees up the memory but when you do it two or three times then you can no longer enter the chaturbate domain as if I couldn't make a connection it just loads forever I have to close and open the browser again to be able to enter the domain.
I hope you understand what I put in the translator. Greetings
asaa
Hello,
I have found two problems with the 5.0.14 version of the script.
My setup:
* Linux Brave browser (Chromium based)
* Tampermonkey v5.1.0
* 12 GB RAM
1.
Produces a memory leak in the Multi Cam Viewer.
The used memory is steady raising until the browser runs out of memory and kill the tab with a "Snap" error.
This takes about 20-30 minutes and is reliable reproducible.
Syslog:
traps: brave[12406] trap invalid opcode ip:5ea8f5b525c8 sp:7ffdbc6e0fe0 error:0 in brave[5ea8ee8d1000+bdd7000]
After crashing all memory get freed and it works again after restart for another 20-30 minutes.
2.
The chaturbate-enhancer script does not keep any settings inclusive all hidden room previews in between browser sessions. It used to keep the settings. This problem may related to the memory leak.
Funny thing, the memory leak does not happen when I have the browser console open. :(
Some browser console log attached anyway.