Created attachment 118801 [details] LO 5.1 Fatal Error - SEH Exception When attempting to add a "Custom Property" of a "Type" of "TEXT" with the property name of "URL", Windows does a Crash of this Application, and the resulting error message is that the App Crashed, with a stand alone error message "LibreOffice 5.1 had a FATAL ERROR", and "SEH Exception - Access Violation". Adding 3 screen shots. The Normal "Custom Properties" Dialogue Box. The Populated "Dialoge Table", and the resulting Crash Message.
Created attachment 118809 [details] custom properties
Created attachment 118810 [details] After Add - on Property
Created attachment 118811 [details] Crash Message from Windows 7
On pc Debian x86-64 with master sources updated today, I don't reproduce this. 32 bits or Windows only bug? Would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)
Created attachment 121287 [details] Text of Backtrace Backtrace added, still Crashes with a SEH Exception.
Recently (today) updated from 5.1.0.alpha+ to 5.1.1.1 (Fresh?) <Install tin hat translator>. Error persists with 5.1.1.1, Unknown if is 32 bit only, as PC is 64 bit CPU Dual Core running Windows 7 Home.
I am *NOT* a programmer, so excuse the cross posting, but found this information useful: http://stackoverflow.com/questions/2782915/what-should-i-know-about-structured-exceptions-seh-in-c Where the discussion includes a link to what SEH is, and how it is implemented in NON-*nix environment.
Richard, there's no backtrace in the file you provided. About SEH, I suppose main devs know about it and I don't think it really helps. Since I usually use Linux for building, retrieving bt, etc., I can't help here. Hopefully, certainly someone could.
It seems Richard got the backtrace steps wrong. Please try again.
(In reply to Beluga from comment #9) > It seems Richard got the backtrace steps wrong. Please try again. Or maybe I am wrong and the crash was not traceable :(
Could you try this as well: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
After Upgrading to LO 5.1.4.x, problem is gone. Does this mean that since the problem was reported in 2015-09, and LO 5.1.4 release date 2016-06, some chunk of code was changed that deals with SEH Exceptions, and the core development team were aware of it, but, instead of finding this particular bug, and describing it here, the sound of crickets is heard? Hmm, funny. But alas, the New Version (5.1.4.2) is now working properly.
SEF exceptions are a very generic category of issues. It's impossible to say what happened, maybe there was another bug report with the same cause that got fixed, or the root of the issues was the same. Or a developer came across such an issue and fixed it (without a bug report existing for it). Glad to hear the bug is gone. Closing this as RESOLVED/WORKSFORME.