When viewing a presentation in "Slide sorter" view, the CPU usage will go to 100% for quite a while, on the order of a minute. This happens with large presentations with lots of graphics. The problem then repeats if a slide is sorted -- that is, after a slide is dragged within the slide sorter view, the CPU usage goes back up to 100% for another minute. At this point, a second slide could be dragged. This makes the slide sorter almost unusable for presentations with graphics.
NOT reproducible with "LibreOffice 3.4.0 – WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:12)]", my own presentation with app. 200 slides, each with jpg image of app. 1 MB. @pete0934@yahoo.com May I ask you to read hints on <http://wiki.documentfoundation.org/BugReport> carefully? Then please: - Attach a test kit with sample documents - Attach screenshots with comments (you can add information using LibO DRAW and then attach your screenshot with comments as PDF) if necessary - Contribute a step by step instruction containing every key press and every mouse click how to reproduce your problem - add information -- what exactly is unexpected -- and why do you believe it's unexpected -- concerning your PC (especially: RAM, Processor, video card) -- concerning your OS distribution / version/ ... -- concerning your LibO version and localization (UI language) –- Libo settings that might be related to your problems (video hardware acceleration ...) -- how you launch LibO -- everything else crossing your mind after you read a.m. URL Can you please file Bug reports with status UNCONFIRMED if your are not absolutely sure that you contributed all required background information and that the problem will be reproducible with information you can provide? Thank you!
Closing Bug due to reporter's inactivity as WFM. @reporter: Please feel free to reopen this bug if you find out that the problem still exists with the current stable LibreOffice version and if you can contribute requested additional information due to <http://wiki.documentfoundation.org/BugReport> (especially BugReport Details)!
RESOLVED, FIXED or CLOSED bugs cant be KEYWORD NEEDINFO.