| commit | 0f5deee363fd0f9f611f4644d662d83380b1a130 | [log] [tgz] |
|---|---|---|
| author | Noel Grandin <noelgrandin@gmail.com> | Thu Mar 26 16:05:06 2026 +0200 |
| committer | Thorsten Behrens <thorsten.behrens@collabora.com> | Fri Mar 27 17:58:55 2026 +0100 |
| tree | 35daa4c8005f1dc6d3e59116cd70d9100f0107b3 | |
| parent | b03f50b0949f8f7f180c6c27f69cc315612e6025 [diff] |
fix crash on Windows in JunitTest_chart2_unoapi no idea what changed to make this happen more often, but it looks like a latent issue. The problem is that the chart code is calling dispose() on vcl stuff, a Toolbox in this case, which happens to be in the middle of a paint, and then the Toolbox crashes. Work around it by adding some more checks for isDisposed(). The disposing stack looks like: 32: ToolBox::dispose - 0x7ff9dbc857d2 31: VclReferenceBase::disposeOnce - 0x7ff9dbeaf969 30: VclPtr<ToolBox>::disposeAndClear - 0x7ff9f451be23 29: framework::`anonymous namespace'::VclToolBarManager::Destroy - 0x7ff9f450d86d 28: framework::ToolBarManager::Destroy - 0x7ff9f450d29b 27: framework::ToolBarManager::dispose - 0x7ff9f451bbf8 26: framework::ToolBarWrapper::dispose - 0x7ff9f4522b61 25: framework::ToolbarLayoutManager::destroyToolbars - 0x7ff9f43a9562 24: framework::ToolbarLayoutManager::reset - 0x7ff9f43b99b3 23: framework::LayoutManager::implts_reset - 0x7ff9f4392c87 22: framework::LayoutManager::frameAction - 0x7ff9f438cb54 21: `anonymous namespace'::XFrameImpl::implts_sendFrameActionEvent - 0x7ff9f4404c85 20: `anonymous namespace'::XFrameImpl::setComponent - 0x7ff9f440a6ed 19: `anonymous namespace'::XFrameImpl::close - 0x7ff9f43fbbea 18: chart::ChartController::notifyClosing - 0x7ff9d529ddbd 17: comphelper::OInterfaceContainerHelper4<com::sun::star::util::XCloseListener>::NotifySingleListener<com::sun::star::lang::EventObject>::operator() - 0x7ff9d54eb919 16: comphelper::OInterfaceContainerHelper4<com::sun::star::util::XCloseListener>::forEach<comphelper::OInterfaceContainerHelper4<com::sun::star::util::XCloseListener>::NotifySingleListener<com::sun::star::lang::EventObject> > - 0x7ff9d54e4f7f 15: comphelper::OInterfaceContainerHelper4<com::sun::star::util::XCloseListener>::notifyEach<com::sun::star::lang::EventObject> - 0x7ff9d54e5157 14: apphelper::CloseableLifeTimeManager::impl_doClose - 0x7ff9d5606c82 13: apphelper::CloseableLifeTimeManager::g_close_endTryClose_doClose - 0x7ff9d5606719 12: chart::ChartModel::close - 0x7ff9d54ee527 11: `anonymous namespace'::cpp_call - 0x7ffa5b9e3d9a 10: unoInterfaceProxyDispatch - 0x7ffa5b9e4e2a 9: binaryurp::IncomingRequest::execute_throw - 0x7ff9f576eed7 8: binaryurp::IncomingRequest::execute - 0x7ff9f576dfb2 7: request - 0x7ff9f578a856 6: cppu_threadpool::JobQueue::enter - 0x7ffa593b7f82 5: cppu_threadpool::ORequestThread::run - 0x7ffa593bfc96 4: threadFunc - 0x7ffa593c083c 3: oslWorkerWrapperFunction - 0x7ffa1190b17a 2: register_onexit_function - 0x7ffa59552ec5 1: BaseThreadInitThunk - 0x7ffa80a67374 0: RtlUserThreadStart - 0x7ffa80e5cc91 Change-Id: I12c2b63ffa2cc84248d19610baf52a5418474b25 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/202748 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
LibreOffice is an integrated office suite based on copyleft licenses and compatible with most document formats and standards. Libreoffice is backed by The Document Foundation, which represents a large independent community of enterprises, developers and other volunteers moved by the common goal of bringing to the market the best software for personal productivity. LibreOffice is open source, and free to download, use and distribute.
A quick overview of the LibreOffice code structure.
You can develop for LibreOffice in one of two ways, one recommended and one much less so. First the somewhat less recommended way: it is possible to use the SDK to develop an extension, for which you can read the API docs and Developers Guide. This re-uses the (extremely generic) UNO APIs that are also used by macro scripting in StarBasic.
The best way to add a generally useful feature to LibreOffice is to work on the code base however. Overall this way makes it easier to compile and build your code, it avoids any arbitrary limitations of our scripting APIs, and in general is far more simple and intuitive - if you are a reasonably able C++ programmer.
These are the current minimal operating system and compiler versions to run and compile LibreOffice, also used by the TDF builds:
Java is required for building many parts of LibreOffice. In TDF Wiki article Development/Java, the exact modules that depend on Java are listed.
The baseline for Java is Java Development Kit (JDK) Version 17 or later.
If you want to use Clang with the LibreOffice compiler plugins, the minimal version of Clang is 12.0.1. Since Xcode doesn't provide the compiler plugin headers, you have to compile your own Clang to use them on macOS.
You can find the TDF configure switches in the distro-configs/ directory.
To setup your initial build environment on Windows and macOS, we provide the LibreOffice Development Environment (LODE) scripts.
For more information see the build instructions for your platform in the TDF wiki.
Each module should have a README.md file inside it which has some degree of documentation for that module; patches are most welcome to improve those. We have those turned into a web page here:
However, there are two hundred modules, many of them of only peripheral interest for a specialist audience. So - where is the good stuff, the code that is most useful. Here is a quick overview of the most important ones:
| Module | Description |
|---|---|
| sal/ | this provides a simple System Abstraction Layer |
| tools/ | this provides basic internal types: Rectangle, Color etc. |
| vcl/ | this is the widget toolkit library and one rendering abstraction |
| framework/ | UNO framework, responsible for building toolbars, menus, status bars, and the chrome around the document using widgets from VCL, and XML descriptions from /uiconfig/ files |
| sfx2/ | legacy core framework used by Writer/Calc/Draw: document model / load/save / signals for actions etc. |
| svx/ | drawing model related helper code, including much of Draw/Impress |
Then applications
| Module | Description |
|---|---|
| desktop/ | this is where the main() for the application lives, init / bootstrap. the name dates back to an ancient StarOffice that also drew a desktop |
| sw/ | Writer |
| sc/ | Calc |
| sd/ | Draw / Impress |
There are several other libraries that are helpful from a graphical perspective:
| Module | Description |
|---|---|
| basegfx/ | algorithms and data-types for graphics as used in the canvas |
| canvas/ | new (UNO) canvas rendering model with various backends |
| cppcanvas/ | C++ helper classes for using the UNO canvas |
| drawinglayer/ | View code to render drawable objects and break them down into primitives we can render more easily. |
Use the "..." form if and only if the included file is found next to the including file. Otherwise, use the <...> form. (For further details, see the mail Re: C[++]: Normalizing include syntax ("" vs <>).)
The UNO API include files should consistently use double quotes, for the benefit of external users of this API.
loplugin:includeform (compilerplugins/clang/includeform.cxx) enforces these rules.
Beyond this, you can read the README.md files, send us patches, ask on the mailing list libreoffice@lists.freedesktop.org (no subscription required) or poke people on IRC #libreoffice-dev on irc.libera.chat - we're a friendly and generally helpful mob. We know the code can be hard to get into at first, and so there are no silly questions.