Bug 94323 - Adding the "Custom Properties" field: URL Causes LO Writer to Crash with SEH Exception: Access Violation
Summary: Adding the "Custom Properties" field: URL Causes LO Writer to Crash with SEH ...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) Master
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2015-09-17 18:47 UTC by Richard_416282
Modified: 2017-02-16 15:42 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

LO 5.1 Fatal Error - SEH Exception (14.73 KB, image/jpeg)
2015-09-17 18:47 UTC, Richard_416282
custom properties (35.08 KB, image/jpeg)
2015-09-17 19:43 UTC, Richard_416282
After Add - on Property (37.05 KB, image/jpeg)
2015-09-17 19:53 UTC, Richard_416282
Crash Message from Windows 7 (46.44 KB, image/jpeg)
2015-09-17 19:54 UTC, Richard_416282
Text of Backtrace (495 bytes, text/plain)
2015-12-14 03:37 UTC, Richard_416282

Note You need to log in before you can comment on or make changes to this bug.
Description Richard_416282 2015-09-17 18:47:43 UTC
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.
Comment 1 Richard_416282 2015-09-17 19:43:43 UTC
Created attachment 118809 [details]
custom properties
Comment 2 Richard_416282 2015-09-17 19:53:15 UTC
Created attachment 118810 [details]
After Add - on Property
Comment 3 Richard_416282 2015-09-17 19:54:30 UTC
Created attachment 118811 [details]
Crash Message from Windows 7
Comment 4 Julien Nabet 2015-09-18 21:56:03 UTC
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)
Comment 5 Richard_416282 2015-12-14 03:37:51 UTC
Created attachment 121287 [details]
Text of Backtrace

Backtrace added, still Crashes with a SEH Exception.
Comment 6 Richard_416282 2016-02-21 04:42:59 UTC
Recently (today) updated from 5.1.0.alpha+ to (Fresh?) <Install tin hat translator>. Error persists with, Unknown if is 32 bit only, as PC is 64 bit CPU Dual Core running Windows 7 Home.
Comment 7 Richard_416282 2016-02-21 04:56:22 UTC
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.
Comment 8 Julien Nabet 2016-02-21 08:36:52 UTC
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.
Comment 9 Buovjaga 2016-02-21 17:20:38 UTC
It seems Richard got the backtrace steps wrong. Please try again.
Comment 10 Buovjaga 2016-02-21 20:02:15 UTC
(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 :(
Comment 11 Buovjaga 2016-03-02 20:01:43 UTC
Could you try this as well: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile

Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 12 Richard_416282 2016-08-07 20:58:11 UTC
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 ( is now working properly.
Comment 13 Aron Budea 2016-08-07 23:09:16 UTC
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.