https://bugs.freedesktop.org/show_bug.cgi?id=55735

          Priority: medium
            Bug ID: 55735
          Assignee: [email protected]
           Summary: Writer hogs cpu after mis-pasting image
          Severity: major
    Classification: Unclassified
                OS: Windows (All)
          Reporter: [email protected]
          Hardware: x86-64 (AMD64)
            Status: UNCONFIRMED
           Version: 3.6.2.2 release
         Component: Writer
           Product: LibreOffice

Created attachment 68218
  --> https://bugs.freedesktop.org/attachment.cgi?id=68218&action=edit
3 page odt doc with images pasted from a google image search result page - the
final 2 images do not display properly and cause Writer to hog cpu and become
unresponsive

A number of times, with both LO 3.6.1 and 3.6.2, my daughter has pasted an
image from the clipboard (copied from a google image search result page) into
an odt doc and the image has been displayed in the document as a empty box with
what looks like the url of the image in a small courier-like font.  The image
is never displayed.  It does not seem to be caused by a particular image type -
I have seen the problem with both gif and png in a document that contains other
gif and png images successfully pasted.

Also, when it happened today with 3.6.2, Writer became unresponsive when I
tried to scroll on the page with the mis-pasted image.  Task Manager shows
soffice.bin*32 spinning at 100% on a cpu.  I can still interact with Writer -
it is not completely stuck - and I can close it though not via the File menu.

This is reproducible for me with the attached example.  If I re-open the odt
doc and try to scroll to the end of the document, the above problem re-occurs.

I never saw this problem with 3.4.* or 3.5.*.

This is on Win7HP 64bit.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to