<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Camerolla Community - (uncategorized)]]></title>
		<link>https://support.camerolla.com/</link>
		<description><![CDATA[Camerolla Community - https://support.camerolla.com]]></description>
		<pubDate>Fri, 10 Apr 2026 22:36:20 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Extensia Lovense pierde logarea?]]></title>
			<link>https://support.camerolla.com/Thread-Extensia-Lovense-pierde-logarea</link>
			<pubDate>Tue, 31 Mar 2026 07:05:09 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Extensia-Lovense-pierde-logarea</guid>
			<description><![CDATA[Salutare,<br />
<br />
Daca se intampla, cu noua extensie Lovense, sa se piarda sesiunea de logare, extensia are nevoie de un hard-refresh in interiorul browserului Camerolla. Iata pasii ce trebuie sa ii faci:<br />
<br />
<img src="https://support.camerolla.com/uploads/manage-extensions.jpg" loading="lazy"  alt="[Image: manage-extensions.jpg]" class="mycode_img" /><br />
<br />
<img src="https://support.camerolla.com/uploads/refresh-extension.jpg" loading="lazy"  alt="[Image: refresh-extension.jpg]" class="mycode_img" />]]></description>
			<content:encoded><![CDATA[Salutare,<br />
<br />
Daca se intampla, cu noua extensie Lovense, sa se piarda sesiunea de logare, extensia are nevoie de un hard-refresh in interiorul browserului Camerolla. Iata pasii ce trebuie sa ii faci:<br />
<br />
<img src="https://support.camerolla.com/uploads/manage-extensions.jpg" loading="lazy"  alt="[Image: manage-extensions.jpg]" class="mycode_img" /><br />
<br />
<img src="https://support.camerolla.com/uploads/refresh-extension.jpg" loading="lazy"  alt="[Image: refresh-extension.jpg]" class="mycode_img" />]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Cum sa reinstalezi Camerolla in situatii de downgrade]]></title>
			<link>https://support.camerolla.com/Thread-Cum-sa-reinstalezi-Camerolla-in-situatii-de-downgrade</link>
			<pubDate>Fri, 27 Mar 2026 18:56:45 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Cum-sa-reinstalezi-Camerolla-in-situatii-de-downgrade</guid>
			<description><![CDATA[Salutare,<br />
<br />
Se poate uneori sa lansez cate un update la Camerolla care inca are erori. Eu fac teste multe, dar nu pot nicicand sa descopar orice posibila problema intrucat nu sunt model ca sa stau si online.<br />
Astfel, pot fi situatii cand anulez un update iar voi veti fi nevoiti (din pacate), sa dezinstalati camerolla si apoi sa reinstalati versiunea mai veche care era ultima data functionala.<br />
<br />
Iata pasii necesari:<br />
<ol type="1" class="mycode_list"><li>dezinstalati Camerolla<br />
</li>
<li>eventual dezinstalati si Camerolla Browser Requirements <br />
<img src="https://support.camerolla.com/uploads/add-remove-programs.jpg" loading="lazy"  alt="[Image: add-remove-programs.jpg]" class="mycode_img" /><br />
</li>
<li>ideal ar fi sa dati si un restart la calculator, sa se curete windows-ul de ce ramane prin registry<br />
</li>
<li>instalati Camerolla din nou (daca nu mai aveti installerul, mergeti pe <a href="https://camerolla.com/latest" target="_blank" rel="noopener" class="mycode_url">https://camerolla.com/latest</a>), urmand toti pasii instalarii<br />
</li>
</ol>
<br />
<br />
<br />
In situatia in care, dupa reinstalare, remarcati ca browserul Camerolla nu porneste, cel mai probabil este deoarece noul profil de chrome existent pe PC-ul tau a fost upgradat la o versiune noua si nu mai este compatibil cu versiunea "mai veche". Din pacate, acest profil va trebui sters, astfel incat Camerolla sa genereze unul nou.<br />
Pasii pt a sterge profilul de Camerolla sunt urmatorii:<br />
<ol type="1" class="mycode_list"><li>deschide Windows Explorer (sau My Computer)<br />
</li>
<li>in bara de sus, scrie <span style="font-weight: bold;" class="mycode_b">%localappdata%</span> si apoi da-i enter<br />
<img src="https://support.camerolla.com/uploads/localappdata.jpg" loading="lazy"  alt="[Image: localappdata.jpg]" class="mycode_img" /><br />
</li>
<li>apoi navigheaza in folderul <span style="font-weight: bold;" class="mycode_b">CygnusTechnologies </span>si de acolo, sterge tot ce gasesti (ar trebui sa ai 2 foldere, Camerolla-Browser si CrashReports)<br />
</li>
<li>apoi reporneste Camerolla, care va genera un profil nou, pe care va trebui sa il configurezi din nou (anume, sa pui adresa URL a panoului si dupa restart, sa configurezi din nou setarile OBS pt site-urile pe care lucrezi)<br />
</li>
</ol>
<br />
<br />
<br />
<br />
Imi pare rau pt astfel de situatii, ma straduiesc sa livrez update-uri perfecte dar, din pacate, sunt si chestii imprevizibile care doar in testare reala pot aparea.]]></description>
			<content:encoded><![CDATA[Salutare,<br />
<br />
Se poate uneori sa lansez cate un update la Camerolla care inca are erori. Eu fac teste multe, dar nu pot nicicand sa descopar orice posibila problema intrucat nu sunt model ca sa stau si online.<br />
Astfel, pot fi situatii cand anulez un update iar voi veti fi nevoiti (din pacate), sa dezinstalati camerolla si apoi sa reinstalati versiunea mai veche care era ultima data functionala.<br />
<br />
Iata pasii necesari:<br />
<ol type="1" class="mycode_list"><li>dezinstalati Camerolla<br />
</li>
<li>eventual dezinstalati si Camerolla Browser Requirements <br />
<img src="https://support.camerolla.com/uploads/add-remove-programs.jpg" loading="lazy"  alt="[Image: add-remove-programs.jpg]" class="mycode_img" /><br />
</li>
<li>ideal ar fi sa dati si un restart la calculator, sa se curete windows-ul de ce ramane prin registry<br />
</li>
<li>instalati Camerolla din nou (daca nu mai aveti installerul, mergeti pe <a href="https://camerolla.com/latest" target="_blank" rel="noopener" class="mycode_url">https://camerolla.com/latest</a>), urmand toti pasii instalarii<br />
</li>
</ol>
<br />
<br />
<br />
In situatia in care, dupa reinstalare, remarcati ca browserul Camerolla nu porneste, cel mai probabil este deoarece noul profil de chrome existent pe PC-ul tau a fost upgradat la o versiune noua si nu mai este compatibil cu versiunea "mai veche". Din pacate, acest profil va trebui sters, astfel incat Camerolla sa genereze unul nou.<br />
Pasii pt a sterge profilul de Camerolla sunt urmatorii:<br />
<ol type="1" class="mycode_list"><li>deschide Windows Explorer (sau My Computer)<br />
</li>
<li>in bara de sus, scrie <span style="font-weight: bold;" class="mycode_b">%localappdata%</span> si apoi da-i enter<br />
<img src="https://support.camerolla.com/uploads/localappdata.jpg" loading="lazy"  alt="[Image: localappdata.jpg]" class="mycode_img" /><br />
</li>
<li>apoi navigheaza in folderul <span style="font-weight: bold;" class="mycode_b">CygnusTechnologies </span>si de acolo, sterge tot ce gasesti (ar trebui sa ai 2 foldere, Camerolla-Browser si CrashReports)<br />
</li>
<li>apoi reporneste Camerolla, care va genera un profil nou, pe care va trebui sa il configurezi din nou (anume, sa pui adresa URL a panoului si dupa restart, sa configurezi din nou setarile OBS pt site-urile pe care lucrezi)<br />
</li>
</ol>
<br />
<br />
<br />
<br />
Imi pare rau pt astfel de situatii, ma straduiesc sa livrez update-uri perfecte dar, din pacate, sunt si chestii imprevizibile care doar in testare reala pot aparea.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Securitate avansata navigand pe internet cu Camerolla]]></title>
			<link>https://support.camerolla.com/Thread-Securitate-avansata-navigand-pe-internet-cu-Camerolla</link>
			<pubDate>Thu, 03 Feb 2022 15:24:34 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Securitate-avansata-navigand-pe-internet-cu-Camerolla</guid>
			<description><![CDATA[Salutare,<br />
<br />
Doresc sa va aduc la cunostinta unul din motivele extrem de importante pentru care ar fi ideal sa folositi browserul Camerolla in detrimentul altor browsere.<br />
<br />
O sa incep prin a va ruga sa cititi intai acest articol original de pe site-ul celor de la Brave, de aici: <a href="https://brave.com/compare/chrome/privacy/" target="_blank" rel="noopener" class="mycode_url">https://brave.com/compare/chrome/privacy/</a><br />
<br />
Dupa cum puteti observa, din ce mentioneaza acestia, ei au adaugat deja functionalitati care ascund activitatea dvs online si NU trimit date (anonim) catre site-urile care incearca sa va "tina urmele" atunci cand stati online, mai ales pe site-urile de videochat.<br />
Mai mult, Camerolla se bazeaza de fapt pe  browserul Brave si peste acesta, am adaugat si functionalitati aditionale atat de securitate cat si de funcitonalitate, care sunt specifice activitatii de videochat.<br />
<br />
Gata, am vorbit destul, ramane sa analizati cu proprii ochi cat mai curand!]]></description>
			<content:encoded><![CDATA[Salutare,<br />
<br />
Doresc sa va aduc la cunostinta unul din motivele extrem de importante pentru care ar fi ideal sa folositi browserul Camerolla in detrimentul altor browsere.<br />
<br />
O sa incep prin a va ruga sa cititi intai acest articol original de pe site-ul celor de la Brave, de aici: <a href="https://brave.com/compare/chrome/privacy/" target="_blank" rel="noopener" class="mycode_url">https://brave.com/compare/chrome/privacy/</a><br />
<br />
Dupa cum puteti observa, din ce mentioneaza acestia, ei au adaugat deja functionalitati care ascund activitatea dvs online si NU trimit date (anonim) catre site-urile care incearca sa va "tina urmele" atunci cand stati online, mai ales pe site-urile de videochat.<br />
Mai mult, Camerolla se bazeaza de fapt pe  browserul Brave si peste acesta, am adaugat si functionalitati aditionale atat de securitate cat si de funcitonalitate, care sunt specifice activitatii de videochat.<br />
<br />
Gata, am vorbit destul, ramane sa analizati cu proprii ochi cat mai curand!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Camerolla is your SECURE browser]]></title>
			<link>https://support.camerolla.com/Thread-Camerolla-is-your-SECURE-browser</link>
			<pubDate>Thu, 03 Feb 2022 15:19:57 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Camerolla-is-your-SECURE-browser</guid>
			<description><![CDATA[Hello,<br />
<br />
We want to tell you why it is highly recommended that you start using Camerolla browser for all activities in your studio.<br />
Please allow yourself to read a bit about this topic on Brave browser: <a href="https://brave.com/compare/chrome/privacy/" target="_blank" rel="noopener" class="mycode_url">https://brave.com/compare/chrome/privacy/</a><br />
<br />
As you can understand from their page, Brave browser already stops all major trackers, so when you browse websites, no data is sent anonymously to various "interested" 3rdparties.<br />
Since our browser, Camerolla, is actually based on Brave browser, we took this further and added a few more customizations to make it better for camming industry, more secure.<br />
<br />
Enough with the chit-chat, start camerolling today <img src="https://support.camerolla.com/images/smilies/smile.png" alt="Smile" title="Smile" class="smilie smilie_1" />]]></description>
			<content:encoded><![CDATA[Hello,<br />
<br />
We want to tell you why it is highly recommended that you start using Camerolla browser for all activities in your studio.<br />
Please allow yourself to read a bit about this topic on Brave browser: <a href="https://brave.com/compare/chrome/privacy/" target="_blank" rel="noopener" class="mycode_url">https://brave.com/compare/chrome/privacy/</a><br />
<br />
As you can understand from their page, Brave browser already stops all major trackers, so when you browse websites, no data is sent anonymously to various "interested" 3rdparties.<br />
Since our browser, Camerolla, is actually based on Brave browser, we took this further and added a few more customizations to make it better for camming industry, more secure.<br />
<br />
Enough with the chit-chat, start camerolling today <img src="https://support.camerolla.com/images/smilies/smile.png" alt="Smile" title="Smile" class="smilie smilie_1" />]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[RO] Explicarea utilizarii CPU in Camerolla-Chrome]]></title>
			<link>https://support.camerolla.com/Thread-RO-Explicarea-utilizarii-CPU-in-Camerolla-Chrome</link>
			<pubDate>Thu, 28 Oct 2021 10:06:32 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-RO-Explicarea-utilizarii-CPU-in-Camerolla-Chrome</guid>
			<description><![CDATA[Salutare,<br />
<br />
Cativa din clienti m-au intrebat de ce sunt atat de multe procese chrome.exe deschise in task manager, de ce unele sunt "background" si alte active, de ce pe 1 pc e doar 1 process background si pe altul 5, etc....<br />
<span style="font-weight: bold;" class="mycode_b">Aceasta abordare este specifica browserului Chrome si este geniala, in sensul ca, daca oricare din site-uri da o eroare si crapa (se inteapa dupa cum ziceti unii), celelalte nu sunt afectate.</span><br />
<br />
Pe scurt, pentru fiecare SITE NOU care il deschizi (fie ca il deschizi in TAB nou, fie ca il deschizi in fereastra noua), <span style="font-weight: bold;" class="mycode_b">cel putin 1 nou chrome.exe se va deschide</span> pt acel site (functie de site).<br />
De asemeni, pentru fiecare extensie instalata in browser, cel putin 1 chrome.exe se va crea, care se ocupa strict de acea extensie.<br />
<br />
Acum, hai sa despicam firul in 4.<br />
De exemple, imediat dupa ce porneste camerolla, daca te uiti in task manager, o sa remarci 11 procese, din care fiecare are cate o functie specifica (desi, tu fizic inca nu ai deschis niciun site):<div style="text-align: center;" class="mycode_align">
<img src="https://support.camerolla.com\images\cpu-explained\01-simple-start-of-browser.JPG" loading="lazy"  alt="[Image: 01-simple-start-of-browser.JPG]" class="mycode_img" /></div> <div style="text-align: justify;" class="mycode_align">Acum, da-mi voie sa explic ce e acolo.<br />
Dupa cum poti observa pe poza mea, atat in zona de task-manager din Chrome, cat si in task managerul din Windows:</div><ul class="mycode_list"><li>sunt 6 procese active<br />
</li>
<li>si 5 procese de tip background (adica, procese care ruleaza... in spate... nu stiu cum sa explic in romana... in paralel cum ar veni)<br />
</li>
</ul>
Procesele active sunt sesiuni de chrome.exe care se ocupa de paginile web deschise, de procese de randare grafica si de extensiile instalate.<br />
De exemplu, din cele 6 procese active din imaginea de mai sus, 2 apartin extensiei Lovense, 1 alt process e din extensia Camerolla si altul din extensia AudioOnly pt YouTube.<br />
Astfel, ca doar altele 2 sunt aplicatia chrome si randarea principala.<div style="text-align: justify;" class="mycode_align">Procele celelalte de tip background sunt de tip randare-background, utilitati si detectia-crashurilor.<br />
De asemeni, 2 din ele sunt specifice paginii "principale" din care modelul deschide site-urile, anume ceea ce se intampla cand apesi CTRL+T sau cand deschizi about:blank<br />
<br />
<img src="https://support.camerolla.com/images/cpu-explained/background-procs-explained.JPG" loading="lazy"  alt="[Image: background-procs-explained.JPG]" class="mycode_img" /><br />
<br />
Dupa cum vezi ca am subliniat cu rosu:</div><ul class="mycode_list"><li>3 sunt rendere (se ocupa de randarea HTML a site-urilor)<br />
</li>
<li>1 este un utilitar chrome<br />
</li>
<li>ultimul se ocupa de detectia si raportarea crashurilor<br />
</li>
</ul>
<div style="text-align: justify;" class="mycode_align">
Acum, daca ma loghez in pagina, dupa ce ma loghez mai apare un proces in plus, anume cel care se ocupa de monitorizarea turei userului:</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/02-after-login.JPG" loading="lazy"  alt="[Image: 02-after-login.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Bonnnnn, acum daca de exemplu deschidem un site, o sa vedeti ca apare inca un chrome.exe, care este "<span style="font-style: italic;" class="mycode_i">vinovatul</span>" pentru deschiderea acestui nou site:</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/03-after-open-1-site.JPG" loading="lazy"  alt="[Image: 03-after-open-1-site.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Si sa-ncerc acum sa exemplific si mai bine treaba cu 1 process pt fiecare site deschis...<br />
Daca mai deschidem inca 2 tab-uri cu LiveJasmin... o sa remarcati inca 2 procese chrome.exe... asa ca numarul nostru total de procese active creste de la opt la zece.<br />
</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/04-after-open-2-more-tabs-with-jasmin.JPG" loading="lazy"  alt="[Image: 04-after-open-2-more-tabs-with-jasmin.JPG]" class="mycode_img" /></div>
Ba mai mult... hai sa simulam ca unul din taburile cu LiveJasmin o sa crashuiasca... (o sa se-ntepe <img src="https://support.camerolla.com/images/smilies/shy.png" alt="Shy" title="Shy" class="smilie smilie_7" /> )<br />
Astfel ca ma duc frumos in task-manager-ul Chrome (SHIFT + ESC pt cei care nu stiu) si aleg unul din cele 3 procese LiveJasmin si apas frumos END TASK. Si ca sa vezi, ca in poza de mai jos, unul din taburi (cel din mijloc in cazul nostru) crapa... si numarul de procese chrome se micsoreaza de la 10 la 9.:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/sample-kill-tab-process.JPG" loading="lazy"  alt="[Image: sample-kill-tab-process.JPG]" class="mycode_img" /></div>
<br />
Acum, pagina principala din care modelul vede graficul cu incasari si poate sa deschida site-urile... acea pagina ocupa si ea:<ul class="mycode_list"><li>un process ca la orice site, care se ocupa de randarea paginii<br />
</li>
<li>si inca 1 care se ocupa de randarea graficului cu incasari<br />
</li>
</ul>
Daca o sa inchidem acum tab-ul acesta, o sa remarci ca 2 din cele 5 procese de tip background or sa dispara:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/after-close-ntp-only-3-background-procs.JPG" loading="lazy"  alt="[Image: after-close-ntp-only-3-background-procs.JPG]" class="mycode_img" /></div>
<br />
Asta nu inseamna ca trebuie sa stati calare pe model sa inchida acel new-tab-page dupa ce-si deschide site-urile... ca nu, nu consuma CPU inutil... doar ca, probabil, va sperie ca exista acolo in lista de procese in task-manager.<br />
<br />
<br />
<br />
Si la final, ca o recapitulare cumva, va rog sa deduceti urmatoarele:<ul class="mycode_list"><li>Chrome-ul camerolla deschide, initial, 10 procese chrome. Asta nu inseamna ca va rupe procesorul in 2... ca in task manager daca va uitati bine, mai gasiti altele cel putin 100 de procese. Dupa cum am explicat mai sus, din cele 10 procese, 2 sunt extensia Lovense, 1 este extensia Camerolla si al 4-lea exte extensia audio-only pt youtube.<br />
</li>
<li>Daca de asemeni, mai adaogi si alte extensii in Camerolla... alea or sa adauge cel putin cate 1 process pt fiecare extensie adaugata de tine.<br />
</li>
<li>Fiecare site nou deschis va adauga un nou chrome.exe in task manager. De exemplu, daca modelul a deshis 5 site-uri + 5 clipuri pe youtube + facebook + google translate, asta inseamna inca 5+5+1+1 adica in 12 procese chrome.exe peste cele 10-11 deschise initial.<br />
</li>
<li>Un website precum MyFreeCams (care are iframes) o sa adauge 2-3 procese in plus... pentru ca fiecare iframe este de fapt un proces separat de chrome. La fel se intampla (daca tin minte bine) si pentru CamContacts.<br />
</li>
<li>De asemeni, luati aminte ca sunt site-uri care ofera ads-uri (cum o face, de exemplu, Chaturbate). Si daca ads-urile alea sunt adaugate ca iframe, asta inseamna noi procese in chrome. uite ca va exemplific treaba asta in poza de mai jos:<br />
</li>
</ul>
<br />
<img src="https://support.camerolla.com/images/cpu-explained/ads-use-more-cpu.JPG" loading="lazy"  alt="[Image: ads-use-more-cpu.JPG]" class="mycode_img" /><br />
<br />
<br />
<br />
Sper din inima ca am explicat cat mai bine ce se intampla in Chrome, si cum functioneaza acesta.<br />
A se nota ca si Firefox are un comportament similar, desi acolo singura diferenta este ca nu se deschide cate un process pt fiecare tab... dar tot sunt multe.... dar acolo daca iti crapa un tab, e cam riscant sa pierzi si in celelalte site-uri deschise.<br />
<br />
Mult succes]]></description>
			<content:encoded><![CDATA[Salutare,<br />
<br />
Cativa din clienti m-au intrebat de ce sunt atat de multe procese chrome.exe deschise in task manager, de ce unele sunt "background" si alte active, de ce pe 1 pc e doar 1 process background si pe altul 5, etc....<br />
<span style="font-weight: bold;" class="mycode_b">Aceasta abordare este specifica browserului Chrome si este geniala, in sensul ca, daca oricare din site-uri da o eroare si crapa (se inteapa dupa cum ziceti unii), celelalte nu sunt afectate.</span><br />
<br />
Pe scurt, pentru fiecare SITE NOU care il deschizi (fie ca il deschizi in TAB nou, fie ca il deschizi in fereastra noua), <span style="font-weight: bold;" class="mycode_b">cel putin 1 nou chrome.exe se va deschide</span> pt acel site (functie de site).<br />
De asemeni, pentru fiecare extensie instalata in browser, cel putin 1 chrome.exe se va crea, care se ocupa strict de acea extensie.<br />
<br />
Acum, hai sa despicam firul in 4.<br />
De exemple, imediat dupa ce porneste camerolla, daca te uiti in task manager, o sa remarci 11 procese, din care fiecare are cate o functie specifica (desi, tu fizic inca nu ai deschis niciun site):<div style="text-align: center;" class="mycode_align">
<img src="https://support.camerolla.com\images\cpu-explained\01-simple-start-of-browser.JPG" loading="lazy"  alt="[Image: 01-simple-start-of-browser.JPG]" class="mycode_img" /></div> <div style="text-align: justify;" class="mycode_align">Acum, da-mi voie sa explic ce e acolo.<br />
Dupa cum poti observa pe poza mea, atat in zona de task-manager din Chrome, cat si in task managerul din Windows:</div><ul class="mycode_list"><li>sunt 6 procese active<br />
</li>
<li>si 5 procese de tip background (adica, procese care ruleaza... in spate... nu stiu cum sa explic in romana... in paralel cum ar veni)<br />
</li>
</ul>
Procesele active sunt sesiuni de chrome.exe care se ocupa de paginile web deschise, de procese de randare grafica si de extensiile instalate.<br />
De exemplu, din cele 6 procese active din imaginea de mai sus, 2 apartin extensiei Lovense, 1 alt process e din extensia Camerolla si altul din extensia AudioOnly pt YouTube.<br />
Astfel, ca doar altele 2 sunt aplicatia chrome si randarea principala.<div style="text-align: justify;" class="mycode_align">Procele celelalte de tip background sunt de tip randare-background, utilitati si detectia-crashurilor.<br />
De asemeni, 2 din ele sunt specifice paginii "principale" din care modelul deschide site-urile, anume ceea ce se intampla cand apesi CTRL+T sau cand deschizi about:blank<br />
<br />
<img src="https://support.camerolla.com/images/cpu-explained/background-procs-explained.JPG" loading="lazy"  alt="[Image: background-procs-explained.JPG]" class="mycode_img" /><br />
<br />
Dupa cum vezi ca am subliniat cu rosu:</div><ul class="mycode_list"><li>3 sunt rendere (se ocupa de randarea HTML a site-urilor)<br />
</li>
<li>1 este un utilitar chrome<br />
</li>
<li>ultimul se ocupa de detectia si raportarea crashurilor<br />
</li>
</ul>
<div style="text-align: justify;" class="mycode_align">
Acum, daca ma loghez in pagina, dupa ce ma loghez mai apare un proces in plus, anume cel care se ocupa de monitorizarea turei userului:</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/02-after-login.JPG" loading="lazy"  alt="[Image: 02-after-login.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Bonnnnn, acum daca de exemplu deschidem un site, o sa vedeti ca apare inca un chrome.exe, care este "<span style="font-style: italic;" class="mycode_i">vinovatul</span>" pentru deschiderea acestui nou site:</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/03-after-open-1-site.JPG" loading="lazy"  alt="[Image: 03-after-open-1-site.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Si sa-ncerc acum sa exemplific si mai bine treaba cu 1 process pt fiecare site deschis...<br />
Daca mai deschidem inca 2 tab-uri cu LiveJasmin... o sa remarcati inca 2 procese chrome.exe... asa ca numarul nostru total de procese active creste de la opt la zece.<br />
</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/04-after-open-2-more-tabs-with-jasmin.JPG" loading="lazy"  alt="[Image: 04-after-open-2-more-tabs-with-jasmin.JPG]" class="mycode_img" /></div>
Ba mai mult... hai sa simulam ca unul din taburile cu LiveJasmin o sa crashuiasca... (o sa se-ntepe <img src="https://support.camerolla.com/images/smilies/shy.png" alt="Shy" title="Shy" class="smilie smilie_7" /> )<br />
Astfel ca ma duc frumos in task-manager-ul Chrome (SHIFT + ESC pt cei care nu stiu) si aleg unul din cele 3 procese LiveJasmin si apas frumos END TASK. Si ca sa vezi, ca in poza de mai jos, unul din taburi (cel din mijloc in cazul nostru) crapa... si numarul de procese chrome se micsoreaza de la 10 la 9.:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/sample-kill-tab-process.JPG" loading="lazy"  alt="[Image: sample-kill-tab-process.JPG]" class="mycode_img" /></div>
<br />
Acum, pagina principala din care modelul vede graficul cu incasari si poate sa deschida site-urile... acea pagina ocupa si ea:<ul class="mycode_list"><li>un process ca la orice site, care se ocupa de randarea paginii<br />
</li>
<li>si inca 1 care se ocupa de randarea graficului cu incasari<br />
</li>
</ul>
Daca o sa inchidem acum tab-ul acesta, o sa remarci ca 2 din cele 5 procese de tip background or sa dispara:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/after-close-ntp-only-3-background-procs.JPG" loading="lazy"  alt="[Image: after-close-ntp-only-3-background-procs.JPG]" class="mycode_img" /></div>
<br />
Asta nu inseamna ca trebuie sa stati calare pe model sa inchida acel new-tab-page dupa ce-si deschide site-urile... ca nu, nu consuma CPU inutil... doar ca, probabil, va sperie ca exista acolo in lista de procese in task-manager.<br />
<br />
<br />
<br />
Si la final, ca o recapitulare cumva, va rog sa deduceti urmatoarele:<ul class="mycode_list"><li>Chrome-ul camerolla deschide, initial, 10 procese chrome. Asta nu inseamna ca va rupe procesorul in 2... ca in task manager daca va uitati bine, mai gasiti altele cel putin 100 de procese. Dupa cum am explicat mai sus, din cele 10 procese, 2 sunt extensia Lovense, 1 este extensia Camerolla si al 4-lea exte extensia audio-only pt youtube.<br />
</li>
<li>Daca de asemeni, mai adaogi si alte extensii in Camerolla... alea or sa adauge cel putin cate 1 process pt fiecare extensie adaugata de tine.<br />
</li>
<li>Fiecare site nou deschis va adauga un nou chrome.exe in task manager. De exemplu, daca modelul a deshis 5 site-uri + 5 clipuri pe youtube + facebook + google translate, asta inseamna inca 5+5+1+1 adica in 12 procese chrome.exe peste cele 10-11 deschise initial.<br />
</li>
<li>Un website precum MyFreeCams (care are iframes) o sa adauge 2-3 procese in plus... pentru ca fiecare iframe este de fapt un proces separat de chrome. La fel se intampla (daca tin minte bine) si pentru CamContacts.<br />
</li>
<li>De asemeni, luati aminte ca sunt site-uri care ofera ads-uri (cum o face, de exemplu, Chaturbate). Si daca ads-urile alea sunt adaugate ca iframe, asta inseamna noi procese in chrome. uite ca va exemplific treaba asta in poza de mai jos:<br />
</li>
</ul>
<br />
<img src="https://support.camerolla.com/images/cpu-explained/ads-use-more-cpu.JPG" loading="lazy"  alt="[Image: ads-use-more-cpu.JPG]" class="mycode_img" /><br />
<br />
<br />
<br />
Sper din inima ca am explicat cat mai bine ce se intampla in Chrome, si cum functioneaza acesta.<br />
A se nota ca si Firefox are un comportament similar, desi acolo singura diferenta este ca nu se deschide cate un process pt fiecare tab... dar tot sunt multe.... dar acolo daca iti crapa un tab, e cam riscant sa pierzi si in celelalte site-uri deschise.<br />
<br />
Mult succes]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Explaining CPU usage]]></title>
			<link>https://support.camerolla.com/Thread-Explaining-CPU-usage</link>
			<pubDate>Thu, 28 Oct 2021 09:31:22 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Explaining-CPU-usage</guid>
			<description><![CDATA[Hello guys,<br />
<br />
Few of you, overtime, asked me they wanted to understad the CPU usage in chrome, and why a number of processes are opened, etc.<br />
Well, this is a chrome-specific behavior, specially designed so that if a website crashes, all others are NOT affected. And this is good.<br />
<br />
Basically, for each NEW SITE that you open (either if in a new tab or if in a new window or popup or if a frame inside other site), at least 1 new chrome.exe process will exist for it.<br />
Also, for each browser extension that is added inside chrome, 1 new chrome.exe process gets created.<br />
<br />
For example, first time you start camerolla app, chrome will start by default with 11 distinct processes, each having a specific job, as you can see in this image:<div style="text-align: center;" class="mycode_align">
<img src="https://support.camerolla.com\images\cpu-explained\01-simple-start-of-browser.JPG" loading="lazy"  alt="[Image: 01-simple-start-of-browser.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">Now, let me explain what's there.<br />
As you can see from Chrome's task manager, and also from Windows' task manager, there are:</div><ul class="mycode_list"><li>6 active processes<br />
</li>
<li>5 background processes<br />
</li>
</ul>
<div style="text-align: justify;" class="mycode_align">The active processes are sessions of chrome that deal with pages and extensions. For example, out of the 6 active processes in the image above, 2 of them are because of Lovense extension, one is because of Camerolla assistant, another one is of YouTube audio-only. The remaining 2 are of main chrome.<br />
<br />
The background processes are sessions of chrome that render the pages in background (paralel), or utilities that monitor crashes, etc, as you will see in the next image. 2 of them for example, are related with the new-tab-page that you see when logging-in.<br />
<br />
<img src="https://support.camerolla.com/images/cpu-explained/background-procs-explained.JPG" loading="lazy"  alt="[Image: background-procs-explained.JPG]" class="mycode_img" /><br />
<br />
As i highlighted in RED, the background processes:</div><ul class="mycode_list"><li>3 are renderers (which render the HTML of websites into visible content)<br />
</li>
<li>1 is a utility<br />
</li>
<li>and one is taking care of reporting crashes<br />
</li>
</ul>
<div style="text-align: justify;" class="mycode_align">
Now... after the user logsin in the app, 1 new process will show-up, which takes care of monitoring user's online times etc:</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/02-after-login.JPG" loading="lazy"  alt="[Image: 02-after-login.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Now, if we also open a new site, you will see that the active processes will increase from 7 to 8, because we will open a new tab (so, a new chrome.exe process):</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/03-after-open-1-site.JPG" loading="lazy"  alt="[Image: 03-after-open-1-site.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Now, to even better explain this, if we open 2 more tabs with livejasmin, you will see 2 more processes... so the number of active chrome.exe processes will change from 8 to 10.</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/04-after-open-2-more-tabs-with-jasmin.JPG" loading="lazy"  alt="[Image: 04-after-open-2-more-tabs-with-jasmin.JPG]" class="mycode_img" /></div>
Now, for the power of example... let's simulate that one of the 3 livejasmin tabs crashes (we will the TAB process from internal Chrome's task manager). You will learn that all other websites are still working, but only the tab that we killed will have crashed, and that the number of active processes decreases from 10 to 9:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/sample-kill-tab-process.JPG" loading="lazy"  alt="[Image: sample-kill-tab-process.JPG]" class="mycode_img" /></div>
<br />
As about the NEW-TAB-PAGE from where the user (model or staff) opens the camsites... that one uses 2 background processes:<ul class="mycode_list"><li>one for rendering the page with camsites, time online, time in break, etc<br />
</li>
<li>the other for rendering the frame with the periodical earnings of the model<br />
</li>
</ul>
If you close that new-tab-page, you will see that the number of background processes decreases from 5 to 3:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/after-close-ntp-only-3-background-procs.JPG" loading="lazy"  alt="[Image: after-close-ntp-only-3-background-procs.JPG]" class="mycode_img" /></div>
<br />
<br />
Now... please understand that:<ul class="mycode_list"><li>Chrome in our standard manner now usually uses at least 10 processes at minimum. This doesn't mean that all of them are CPU intensive, no... but they are indeed processes that might scare you. As explained, out of the 10, 2 are of Lovense extension, one is of Camerolla extension, one is of YuTube audio only extension.<br />
</li>
<li>If you also add more extensions to chrome, those will increase the number of processes, depending on the extensions you add.<br />
</li>
<li>Each TAB page (or window) ads at least 1 more process. So if the model opened 5 websites and 5 youtube pages, and 1 google translate and one facebook... that means 5+5+1+1 = 12 more CPU processes added to those initial 10.<br />
</li>
<li>A website like MyFreeCams which uses frames, most probably will add 2 processes or so. Might also be valid for CamContacts for example<br />
</li>
<li>Also, some websites (like chaturbate for example) are distributin ADS as iframes... and each add comes with a cost of a new CPU process in chrome! Even tracking via Google which gets added on sites might also add a new CPU process in chrome, as you can learn from the picture bellow:<br />
</li>
</ul>
<img src="https://support.camerolla.com/images/cpu-explained/ads-use-more-cpu.JPG" loading="lazy"  alt="[Image: ads-use-more-cpu.JPG]" class="mycode_img" /><br />
<br />
<br />
<br />
I honestly hope that you understand, from this topic, how Chrome wroks.<br />
Please note that Firefox works in a simila fashion, but in its case, the number of processes is smaller... but it is better exposed to crash-risks compared to Chrome due to its design.]]></description>
			<content:encoded><![CDATA[Hello guys,<br />
<br />
Few of you, overtime, asked me they wanted to understad the CPU usage in chrome, and why a number of processes are opened, etc.<br />
Well, this is a chrome-specific behavior, specially designed so that if a website crashes, all others are NOT affected. And this is good.<br />
<br />
Basically, for each NEW SITE that you open (either if in a new tab or if in a new window or popup or if a frame inside other site), at least 1 new chrome.exe process will exist for it.<br />
Also, for each browser extension that is added inside chrome, 1 new chrome.exe process gets created.<br />
<br />
For example, first time you start camerolla app, chrome will start by default with 11 distinct processes, each having a specific job, as you can see in this image:<div style="text-align: center;" class="mycode_align">
<img src="https://support.camerolla.com\images\cpu-explained\01-simple-start-of-browser.JPG" loading="lazy"  alt="[Image: 01-simple-start-of-browser.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">Now, let me explain what's there.<br />
As you can see from Chrome's task manager, and also from Windows' task manager, there are:</div><ul class="mycode_list"><li>6 active processes<br />
</li>
<li>5 background processes<br />
</li>
</ul>
<div style="text-align: justify;" class="mycode_align">The active processes are sessions of chrome that deal with pages and extensions. For example, out of the 6 active processes in the image above, 2 of them are because of Lovense extension, one is because of Camerolla assistant, another one is of YouTube audio-only. The remaining 2 are of main chrome.<br />
<br />
The background processes are sessions of chrome that render the pages in background (paralel), or utilities that monitor crashes, etc, as you will see in the next image. 2 of them for example, are related with the new-tab-page that you see when logging-in.<br />
<br />
<img src="https://support.camerolla.com/images/cpu-explained/background-procs-explained.JPG" loading="lazy"  alt="[Image: background-procs-explained.JPG]" class="mycode_img" /><br />
<br />
As i highlighted in RED, the background processes:</div><ul class="mycode_list"><li>3 are renderers (which render the HTML of websites into visible content)<br />
</li>
<li>1 is a utility<br />
</li>
<li>and one is taking care of reporting crashes<br />
</li>
</ul>
<div style="text-align: justify;" class="mycode_align">
Now... after the user logsin in the app, 1 new process will show-up, which takes care of monitoring user's online times etc:</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/02-after-login.JPG" loading="lazy"  alt="[Image: 02-after-login.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Now, if we also open a new site, you will see that the active processes will increase from 7 to 8, because we will open a new tab (so, a new chrome.exe process):</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/03-after-open-1-site.JPG" loading="lazy"  alt="[Image: 03-after-open-1-site.JPG]" class="mycode_img" /></div><div style="text-align: justify;" class="mycode_align">
Now, to even better explain this, if we open 2 more tabs with livejasmin, you will see 2 more processes... so the number of active chrome.exe processes will change from 8 to 10.</div><div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/04-after-open-2-more-tabs-with-jasmin.JPG" loading="lazy"  alt="[Image: 04-after-open-2-more-tabs-with-jasmin.JPG]" class="mycode_img" /></div>
Now, for the power of example... let's simulate that one of the 3 livejasmin tabs crashes (we will the TAB process from internal Chrome's task manager). You will learn that all other websites are still working, but only the tab that we killed will have crashed, and that the number of active processes decreases from 10 to 9:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/sample-kill-tab-process.JPG" loading="lazy"  alt="[Image: sample-kill-tab-process.JPG]" class="mycode_img" /></div>
<br />
As about the NEW-TAB-PAGE from where the user (model or staff) opens the camsites... that one uses 2 background processes:<ul class="mycode_list"><li>one for rendering the page with camsites, time online, time in break, etc<br />
</li>
<li>the other for rendering the frame with the periodical earnings of the model<br />
</li>
</ul>
If you close that new-tab-page, you will see that the number of background processes decreases from 5 to 3:<div style="text-align: center;" class="mycode_align"><img src="https://support.camerolla.com/images/cpu-explained/after-close-ntp-only-3-background-procs.JPG" loading="lazy"  alt="[Image: after-close-ntp-only-3-background-procs.JPG]" class="mycode_img" /></div>
<br />
<br />
Now... please understand that:<ul class="mycode_list"><li>Chrome in our standard manner now usually uses at least 10 processes at minimum. This doesn't mean that all of them are CPU intensive, no... but they are indeed processes that might scare you. As explained, out of the 10, 2 are of Lovense extension, one is of Camerolla extension, one is of YuTube audio only extension.<br />
</li>
<li>If you also add more extensions to chrome, those will increase the number of processes, depending on the extensions you add.<br />
</li>
<li>Each TAB page (or window) ads at least 1 more process. So if the model opened 5 websites and 5 youtube pages, and 1 google translate and one facebook... that means 5+5+1+1 = 12 more CPU processes added to those initial 10.<br />
</li>
<li>A website like MyFreeCams which uses frames, most probably will add 2 processes or so. Might also be valid for CamContacts for example<br />
</li>
<li>Also, some websites (like chaturbate for example) are distributin ADS as iframes... and each add comes with a cost of a new CPU process in chrome! Even tracking via Google which gets added on sites might also add a new CPU process in chrome, as you can learn from the picture bellow:<br />
</li>
</ul>
<img src="https://support.camerolla.com/images/cpu-explained/ads-use-more-cpu.JPG" loading="lazy"  alt="[Image: ads-use-more-cpu.JPG]" class="mycode_img" /><br />
<br />
<br />
<br />
I honestly hope that you understand, from this topic, how Chrome wroks.<br />
Please note that Firefox works in a simila fashion, but in its case, the number of processes is smaller... but it is better exposed to crash-risks compared to Chrome due to its design.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Comments and opinions regarding BETA-2]]></title>
			<link>https://support.camerolla.com/Thread-Comments-and-opinions-regarding-BETA-2</link>
			<pubDate>Sat, 09 Oct 2021 10:32:17 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Comments-and-opinions-regarding-BETA-2</guid>
			<description><![CDATA[Hello guys,<br />
<br />
Please post here your opinion, feedback and suggestions about the BETA no2 launched on 9th october 2021.]]></description>
			<content:encoded><![CDATA[Hello guys,<br />
<br />
Please post here your opinion, feedback and suggestions about the BETA no2 launched on 9th october 2021.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Comentarii si pareri despre BETA-2]]></title>
			<link>https://support.camerolla.com/Thread-Comentarii-si-pareri-despre-BETA-2</link>
			<pubDate>Sat, 09 Oct 2021 10:31:31 +0300</pubDate>
			<dc:creator><![CDATA[<a href="https://support.camerolla.com/member.php?action=profile&uid=1">sebi</a>]]></dc:creator>
			<guid isPermaLink="false">https://support.camerolla.com/Thread-Comentarii-si-pareri-despre-BETA-2</guid>
			<description><![CDATA[Salutare,<br />
<br />
Va rog comentati aici cu parerile, opiniile si experienta voastra cu BETA-ul nr 2 (lansat pe 9 octombrie 2021)]]></description>
			<content:encoded><![CDATA[Salutare,<br />
<br />
Va rog comentati aici cu parerile, opiniile si experienta voastra cu BETA-ul nr 2 (lansat pe 9 octombrie 2021)]]></content:encoded>
		</item>
	</channel>
</rss>