[Libreoffice-bugs] [Bug 142022] Crash in: mergedlo.dll / on close

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #19 from V Stuart Foote <vstuart.foote at utsa.edu> ---
(In reply to Nico from comment #16)
> Hey !
> Yes, a challenge and hassle but am not alone, hopefully ;o)

;-)

> Main issue is there for the now : which version of LO should I install and
> run ? Puzzled with 7.1 and 7.2 from manual and downloads ?
> Does 7.1 stands for 7.1.1.x ?

No, I was not clear, you did great! 

Next to rule-out issue has already been corrected, you would need to test
against a nightly build of master/7.2, except it would be installed in parallel
as a /a Administrative install. 

Guidance is here [1], but pay attention to complete the 'User configuration'
section to isolate each install from your own Windows user account.

To explain a bit more, 7.1 is the "Fresh" release branch and 7.1.3.2 is just
the latest incremental release build of that branch. The release builds are
archived and include HASH and Mirror details so you can conveniently download
[2].

You said you had no issues with a 7.0 "Still" incremental 7.0.5 build, and this
crash on close of Calc started with a 7.1 release 7.1.2.2 build.  So some
change has been included in the 7.1 branch that is affecting your system.

The current development master branch against a 7.2 release, and there are
nightly test builds on our TinderBox infrastructure.  TB77 is rolling out
nightly builds of Windows 64-bit builds of current master against what will
become a 7.2 release. [3]

An issue that can be reproduced on current master builds with consistent "Steps
to Reproduce" (STR) with a good back trace/stack trace from a release with
symbols helps the devs identify what is happening.  But the TB77 nightly
Windows builds don't include symbols. 

Obtaining a useful stack trace with symbols against master would require a full
Windows Studio install and git fetch of the source to build LibreOffice
locally--just like a TinderBox--except you'd have the symbols and source code
to run the WinDbg against. We don't expect you to do that!

We just need reproducible STR, and sometimes a problem document to work
against. The automated crash reports and now the WinDbg traces you've done also
help immensely.  We just need to figure out why installs on your system are
crashing but seemingly no one else--Julian and I can not reproduce. Hence his
question about memory manager or other 3rd party apps.

Thanks!

=-refs-=
[1] https://wiki.documentfoundation.org/Installing_in_parallel 
[2] https://downloadarchive.documentfoundation.org/libreoffice/old/
[3] https://dev-builds.libreoffice.org/daily/master/

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210502/6b08dab9/attachment.htm>