On Wed, 2011-11-02 at 05:55 +0100, Jean-Baptiste Faure wrote:
Build in progress. :-)
With the fix by Bjoern, smoketest does not block anymore my tests. And I
confirm that your fix solves the CPU problem for me.
Wonderful :-) good to know.
Thank you very much
Thanks for
On Sat, 2011-10-29 at 07:12 +0200, Jean-Baptiste Faure wrote:
In Writer: open a new text document and do nothing else = CPU ~100% of
one core
Should be fixed in master :-) more testing of course much appreciated.
Thanks !
Michael.
--
michael.me...@suse.com
Le 01/11/2011 14:02, Michael Meeks a écrit :
On Sat, 2011-10-29 at 07:12 +0200, Jean-Baptiste Faure wrote:
In Writer: open a new text document and do nothing else = CPU ~100% of
one core
Should be fixed in master :-) more testing of course much appreciated.
Thanks !
Hi Michael,
Le 01/11/2011 14:14, Jean-Baptiste Faure a écrit :
Le 01/11/2011 14:02, Michael Meeks a écrit :
On Sat, 2011-10-29 at 07:12 +0200, Jean-Baptiste Faure wrote:
In Writer: open a new text document and do nothing else = CPU ~100% of
one core
Should be fixed in master :-) more
On Sat, 2011-10-29 at 17:38 -0400, Kevin Hunter wrote:
I don't specifically, but my hunch is that it's some interaction with
the newly merged GTK code.
Almost certainly it's my fault ;-) I'll dig into it later today -
thanks for the testing feedback.
ATB,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/10/11 23:59, Arno Teigseth wrote:
6000 calls/second to Application::Yield in
core/vcl/source/app/svapp.cxx (I think)
ok I reverted to the commit 40360820036a5d6a3359d1b5ec748a47a7edd85f
(from Tue Oct 25 13:50:37 2011 +0300),
just before the
At 1:12am -0400 Sat, 29 Oct 2011, Jean-baptiste Faure wrote:
I already noticed these cpu problems in my own build since 2 or 3
days, but I can't be more precise.
Does somebody has a clue about the cause (which commit?) of this CPU
consumption?
I don't specifically, but my hunch is that it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/10/11 16:38, Kevin Hunter wrote:
At 1:12am -0400 Sat, 29 Oct 2011, Jean-baptiste Faure wrote:
I already noticed these cpu problems in my own build since 2 or
3 days, but I can't be more precise.
Does somebody has a clue about the cause
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/10/11 21:20, Arno Teigseth wrote:
What puzzles me is that LO isn't very slow, it's just using lots of
CPU...
Eh, I'd like to correct that. Just opened a document and it's very
slow. The doc is just about 3200 pages, but it takes forever to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK thanks to moggi on libreoffice-dev irc, I installed valgrind.
Found that running in one terminal:
valgrind --trace-children=yes --tool=callgrind ./swriter
and in another terminal, after about 2 mins of empty swriter document
idle doing this:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/10/11 22:06, Arno Teigseth wrote:
I don't have a clue about how to interpret this. But if these are
function calls, maybe about a million calls are much?
tried with kcachegrind:
6000 calls/second to Application::Yield in
Hi,
Current master daily build (2011-10-28_12.04.03 : LibO-dev 3.5.0
Build ID: 2a91e5b-522e9fe-c4051ff-3b66bd0-672ed49) has a problem that
was not in the previous daily build (2011-10-24_10.58.48):
In Writer: open a new text document and do nothing else = CPU ~100% of
one core
In Calc : open a
12 matches
Mail list logo
