Bug 145171 - Use of questionable polygon optimization on startup
Summary: Use of questionable polygon optimization on startup
Status: RESOLVED DUPLICATE of bug 144113
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.0.0 alpha0+
Hardware: All Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: console-noise
  Show dependency tree / graph
 
Reported: 2021-10-16 16:16 UTC by Eyal Rozenberg
Modified: 2023-12-10 23:33 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2021-10-16 16:16:20 UTC 
What running a daily build (via the libreofficedev7.3 binary), I get - within some other console noise - this message, repeated 7 times:

warn:legacy.tools:2814:2814:tools/source/generic/poly.cxx:1033: Optimizing could fail with beziers!

Obviously this should not happen. I assume some polygons are being drawn - as part of the LO UI, not a document of mine. So, if LO is using some failure-prone polygon drawing routine - it should be fixed, or not used. And if it's not really failure-prone in this context, this should be determined and no warning issued.
Comment 1 Eyal Rozenberg 2021-10-16 16:17:57 UTC 
Build info:

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: c998691e22ceda15c89d55cf7005201f0392dadb
CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: en-US (en_IL); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-10-14_11:54:20
Calc: threaded
Comment 2 Telesto 2021-10-17 09:06:09 UTC 
@Julien
This needs console output
Comment 3 Julien Nabet 2021-10-17 09:13:51 UTC 
Telesto: what do you mean?
Isn't "warn:legacy.tools:2814:2814:tools/source/generic/poly.cxx:1033: Optimizing could fail with beziers!" already a console input?
Comment 4 sdc.blanco 2023-12-10 23:33:14 UTC 

*** This bug has been marked as a duplicate of bug 144113 ***