https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #19 from QA Administrators ---
Dear Alexandre Bibeau,
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not be
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
BogdanB changed:
What|Removed |Added
Blocks||136524
CC|
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #18 from Alexandre Bibeau ---
On my machine, this bug is still present in the latest version.
Here's the exact build:
Version: 6.2.2.2 (x64)
Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d
CPU threads: 8; OS: Windows 10.0
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #17 from QA Administrators ---
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to ret
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #16 from Alexandre Bibeau ---
(In reply to Buovjaga from comment #15)
> (In reply to Alexandre Bibeau from comment #14)
> > In the meantime, what do I do with that 1GB dump?
>
> How small does it get, if you compress it using
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #15 from Buovjaga ---
(In reply to Alexandre Bibeau from comment #14)
> In the meantime, what do I do with that 1GB dump?
How small does it get, if you compress it using .tar.xz?
--
You are receiving this mail because:
You
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #14 from Alexandre Bibeau ---
I created a process dump during high cpu usage with the windows task manager,
but it gives me a 1GB file...
The instructions for making a dump file using Sysinternals aren't particularly
clear an
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Timur changed:
What|Removed |Added
Priority|medium |low
CC|gti...@gmail.com
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Telesto changed:
What|Removed |Added
CC||gti...@gmail.com
--- Comment #12 from
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Alexandre Bibeau changed:
What|Removed |Added
Version|6.0.1.1 release |6.0.0.3 release
--
You are r
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Alexandre Bibeau changed:
What|Removed |Added
Attachment #140765|longer verysleepy capture |longer verysleepy capture
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #10 from Alexandre Bibeau ---
Created attachment 140765
--> https://bugs.documentfoundation.org/attachment.cgi?id=140765&action=edit
longer verysleepy capture of offending thread
Another verysleepy capture, one thread was r
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Buovjaga changed:
What|Removed |Added
Keywords||haveBacktrace
--
You are receiving t
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #9 from Alexandre Bibeau ---
Created attachment 140667
--> https://bugs.documentfoundation.org/attachment.cgi?id=140667&action=edit
verysleepy profile during high CPU usage
While soffice.bin was using about 65% of a core wh
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #8 from Telesto ---
(In reply to Buovjaga from comment #7)
> (In reply to Alexandre Bibeau from comment #6)
> > (In reply to Buovjaga from comment #5)
> > > Ok, I guess we have to set to NEW, but it's darn hard to reproduce an
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Xisco Faulí changed:
What|Removed |Added
Keywords|bibisectRequest |notBibisectable
--
You are receiv
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Xisco Faulí changed:
What|Removed |Added
Keywords||bibisectRequest
CC
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #7 from Buovjaga ---
(In reply to Alexandre Bibeau from comment #6)
> (In reply to Buovjaga from comment #5)
> > Ok, I guess we have to set to NEW, but it's darn hard to reproduce and
> > investigate.
>
> Is there some sort o
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #6 from Alexandre Bibeau ---
(In reply to Buovjaga from comment #5)
> Ok, I guess we have to set to NEW, but it's darn hard to reproduce and
> investigate.
Is there some sort of diagnostics tool I can run? It happens fairly
c
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
Buovjaga changed:
What|Removed |Added
Keywords||regression
Status|UNCONFI
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #4 from Alexandre Bibeau ---
I have also been able to replicate the bug with .odt documents. Again, they
contain nothing special, just text and comments.
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #3 from Tim ---
I can confirm I also suffer from this, or a similar, bug.
In my case after a document has been left open for multiple hours or days
Writer begins using 100% of a single CPU core.
I am using .odt documents of
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #2 from Alexandre Bibeau ---
(In reply to Imai from comment #1)
> Issue not reproduced.
> I tried 3hours,but not around 20%.
> ---
> OS X EL Capitan
> Ver:10.11.3
>
> version: 6.0.1.1
> Build ID: 60bfb1526849283ce2491346ed2aa
https://bugs.documentfoundation.org/show_bug.cgi?id=115845
--- Comment #1 from Imai <14m4...@kobe-du.ac.jp> ---
Issue not reproduced.
I tried 3hours,but not around 20%.
---
OS X EL Capitan
Ver:10.11.3
version: 6.0.1.1
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU threads: 4; OS:Mac OS X
24 matches
Mail list logo
