https://bugs.documentfoundation.org/show_bug.cgi?id=153510

            Bug ID: 153510
           Summary: Conditional formatting with STYLE and incorrect (case)
                    style name -> continuous CPU consumption, menus not
                    drawn in some UI renders
           Product: LibreOffice
           Version: 5.1.0.3 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 185277
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185277&action=edit
STYLE in conditional formatting

The attached spreadsheet (FODT, simplified to bare minimum) has two cells
(A1:A2) with conditional formatting having STYLE function that tries to set a
style name differing (in character case) from the style name present in the
document: it uses "STYLE(A1)" formula. The content of the cells is "A"; the
style in the document is named "a" (and it gets applied to the cells, as one
can see in the stylist).

Since v.5.1, opening it and having the two cells in view, results in continuous
100% CPU consumption (single core). In that version, using OpenGL (Windows),
menus still were working OK.

Since v.5.2, using OpenGL, menus are shown blank (likely, the priority of
drawing their content is lower than the priority of the continuous processing
taking the 100% of a core). Disabling OpenGL, the menus are drawn OK, but the
CPU consumption is unchanged (so the menu drawing priority is obviously
different).

In current master, Skia works the same way as OpenGL in old versions (now
showing menus when the cells are in view; likely because it was modelled after
OpenGL render, and has similar priorities). As before, not using Skia still
shows continuous CPU consumption.

Changing cells' content from "A" to "a" (to match case of actual style) stops
the CPU consumption.

The usefulness of using STYLE in conditional formatting is not a matter here,
only the wrong effects.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to