soffice.bin crashes with ntdll.dll on very first startup (splash - crash) and every time on close the last document. OS: Windows Server 2008 / Windows Server 2008 R2 LibO: 5.3.2.2
For the test, coud lso rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?
Negative. New profile crashes too.
You could try this to get a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Automation
Created attachment 132534 [details] Backtrace - Crash on first startup (Windows Server 2008) OS - Windows Server 2008 SP2 with latest updates / Windows Server 2008 R2 SP1 with latest updates LibO - 5.3.2 Steps to reproduce: 1) Install LibO 5.3.2 OR delete/rename old profile folder if 5.3.2 version is already installed 2) Start LibO 3) You will get crash on first startup 4) You will get crash on every exit In my case problem reproducible since LibO 5.3.2.1 ONLY on Server 2008 / 2008 R2. LibO 5.3.2 works without crashes on Windows 7. LibO 5.3.1 works without crashes on ALL Windows.
Created attachment 132535 [details] Backtrace - Crash on exit (Windows Server 2008 R2)
both of these traces are DllMain running global variable dtors, with this static D2DWriteTextOutRenderer in vcl/win/gdi/winlayout.cxx being the likely culprit: TextOutRenderer & TextOutRenderer::get(bool bUseDWrite) { if (bUseDWrite) { static std::unique_ptr<TextOutRenderer> _impl(D2DWriteTextOutRenderer::InitModules() ? static_cast<TextOutRenderer*>(new D2DWriteTextOutRenderer()) : static_cast<TextOutRenderer*>(new ExTextOutRenderer)); return *_impl; } speculating why this crashes: the crash is inside a ThreadManager_VistaThreadPool::~ThreadManager_VistaThreadPool, and at this point in shutdown only the thread that has called exit() is still running, all other threads have been terminated by Win32 already, so maybe this wants to access something that is no longer there. i wonder if it would help to move the instance somewhere where it can be deleted from DeInitVCL()? it shouldn't be needed after DeInitVCL() hopefully?
okay, Raymond Chen says doing this is stupid https://blogs.msdn.microsoft.com/oldnewthing/20120427-00/?p=7763/
should be fixed on master
Michael Stahl committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=df556aa47da22f96b3fcd356c12419d3035cba3c tdf#106933 vcl: delete D2DWriteTextOutRenderer before exit() It will be available in 5.4.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
And what about 5.3 branch?
Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-5-3": http://cgit.freedesktop.org/libreoffice/core/commit/?id=1ba5bae490f7e14e475e0b80f03e5f444cdce908&h=libreoffice-5-3 tdf#106933 vcl: delete D2DWriteTextOutRenderer before exit() It will be available in 5.3.3. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.