Bug 155895 - general protection fault when try to destroy LibreOfficeKit
Summary: general protection fault when try to destroy LibreOfficeKit
Status: RESOLVED DUPLICATE of bug 166219
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: LibreOfficeKit
  Show dependency treegraph
 
Reported: 2023-06-17 10:39 UTC by Sean Pan
Modified: 2026-01-22 06:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Pan 2023-06-17 10:39:21 UTC
Description:
 general protection fault when invoking void (*destroy) (LibreOfficeKit* pThis)

[Sat Jun 17 18:05:31 2023] traps: libreoffice-kit-debug[26808] general protection fault ip:7ff1f15bb3e9 sp:7ffc00c8b970 error:0 in libmergedlo.so[7ff1f0014000+2d90000]

early version works fine ,such as 6.4.7.2


Steps to Reproduce:
1.use lok_init() to initialize a LibreOfficeKit instance 
2.destroy it 
3.

Actual Results:
general protection fault logging in kern.log

Expected Results:
program should exit 


Reproducible: Always


User Profile Reset: No

Additional Info:
LibreOffice 7.3.7.2 30(Build:2)
Comment 1 Buovjaga 2026-01-21 16:41:39 UTC
Hossein: you have experimented with LibreOfficeKit quite a lot. What do you think about this init and destruction?
Comment 2 Hossein 2026-01-22 05:48:55 UTC
(In reply to Buovjaga from comment #1)
> Hossein: you have experimented with LibreOfficeKit quite a lot. What do you
> think about this init and destruction?
A bibisect can tell the exact cause, but anyway I think this is a duplicate of tdf#165025 and/or tdf#166219 from me, which provides more information. tdf#166219 comment 1 from Miklos is informative. The stack trace between these two is different, but they both seem to describe the same problem.
Comment 3 Buovjaga 2026-01-22 06:22:14 UTC
Thanks, let's close as dupe for now.

*** This bug has been marked as a duplicate of bug 166219 ***