<div dir="ltr">We have patches in review that should fix this in 3.6.5. The underlying problem is a couple of JavaScript memory leaks.<div><br></div><div>Best wishes,</div><div>Greg</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 8, 2016 at 10:41 AM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Fri, Jan 8, 2016 at 4:42 PM, Alexander Wels <<a href="mailto:awels@redhat.com">awels@redhat.com</a>> wrote:<br>
> On Friday, January 08, 2016 04:29:47 PM Nir Soffer wrote:<br>
>> On Fri, Jan 8, 2016 at 1:13 PM, Nathanaël Blanchet <<a href="mailto:blanchet@abes.fr">blanchet@abes.fr</a>> wrote:<br>
>> > Hi all,<br>
>> ><br>
>> > Since I upgraded engine to 3.6, I noticed that the webadmin takes a lot of<br>
>> > ressources whatever is the browser. It can become very slow even for small<br>
>> > actions, like changing tabs or editing a vm. The browser activity becomes<br>
>> > intensive (100% of cpu) and the processor very hot with a increased fan<br>
>> > activity. I suppose javascript to be responsible of this behaviour. Is<br>
>> > there a way to reduce the resource allocated to the webadmin?<br>
>> > (This is not a weakness of my laptop which is an i7 cpu with 16GB of RAM)<br>
>><br>
>> Sounds like <a href="https://bugzilla.redhat.com/1264809" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1264809</a><br>
>><br>
>> It was closed because we could not reproduce it with current versions.<br>
>><br>
>> I would try first to upgrade to latest 3.6 version, and if you can reproduce<br>
>> it, please reopen this bug.<br>
>><br>
>> Alexander: can you advice on how to debug this?<br>
>><br>
>> Nir<br>
><br>
> If you are willing to spend some time helping us debug that would be great as<br>
> obviously we are unable to reproduce. If you have Chrome, can you open the<br>
> development tools (ctrl-shift-i) and go to the 'Profiles' tab. That should give<br>
> you the option to 'Collect Javascript CPU Profile' among other things. Make<br>
> sure you select that, and click start. Then go in the web admin and do<br>
> something that makes your CPU spike. Let it go for a little bit doesn't have<br>
> to be long.<br>
><br>
> Go back to the CPU profiles tab and click stop. That will generate a profile and<br>
> that profile will include the percentage of CPU usage per method. It should be<br>
> sorted by percentage. If you can take a screen shot of that and give me the<br>
> exact rpm version, I can use that to de-obfuscate the method name and<br>
> hopefully get some useful information.<br>
<br>
</div></div>You can also save such profile to file, and attach it to the bug.<br>
<br>
When I reorted this, this was also reproducible in Firefox, and both profiles<br>
are attached to the bug.<br>
<span class="HOEnZb"><font color="#888888"><br>
Nir<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Greg Sheremeta, MBA<br>Red Hat, Inc.<br>Sr. Software Engineer<br><a href="mailto:gshereme@redhat.com" target="_blank">gshereme@redhat.com</a><br>919-741-4016<br></div>
</div>