Bug 135066 - Freeze UI and Crash: Insert secondly table from Tab on writer document that is inserted impress
Summary: Freeze UI and Crash: Insert secondly table from Tab on writer document that i...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
7.0.0.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2020-07-23 01:40 UTC by sawakaze
Modified: 2022-10-17 17:29 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
ScreenCast (1.41 MB, video/x-matroska)
2020-07-23 01:40 UTC, sawakaze
Details
I got an error and it crashed. (92.26 KB, image/png)
2020-07-27 23:52 UTC, Junichi Matsukawa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sawakaze 2020-07-23 01:40:00 UTC
Description:
After following step, application is freeze.
(on case of windows, application crash is caused)

On my env, freeze not only libreoffice UI, but also desktop env.
Attachment screencast is detail, please confirm this video.



Steps to Reproduce:
1. open writer 
2. set UI to Tabbed UI
-> writer UI to Tab UI
3. close writer

4. open impress
note: impress is not Tabbed UI
5. Insert > Object > OLE object
6. select LiberOffice Text 
-> insert writer text on presentation
7. select inserted Writer object
8. select "Insert Tab" and Table icon.
9. input table size on table dialog and enter button
-> insert table (it name to "1st table")
10. once click outside oleobject.
11. re-select writer object.
12. cursor set next to "1st table"
13. select table from tab
14. input size and press enter.
-> after press enter, Freeze UI


Actual Results:
Freeze UI.
can not set 2nd table from tabui

Expected Results:
not Freeze UI
can set 2nd table from tabui


Reproducible: Always


User Profile Reset: Yes



Additional Info:
I confirm following version.

Version: 7.0.0.2
Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c
CPU threads: 4; OS:Linux 4.15; UI render: default; VCL: gtk3
Locale: ja-JP (ja_JP.UTF-8); UI: ja-JP
Calc: threaded
Comment 1 sawakaze 2020-07-23 01:40:26 UTC
Created attachment 163432 [details]
ScreenCast
Comment 2 sawakaze 2020-07-23 02:33:54 UTC
I think key point is

1. impress is not tabUI, but writer is tabUI
2. on Step10, user selects other object. and re-select oleobject.
3. operate from tabUI button.
Comment 3 Junichi Matsukawa 2020-07-27 23:52:48 UTC
Created attachment 163661 [details]
I got an error and it crashed.

The bug was reproduced.
I got an error and it crashed.

I used the Separate Install GUI.
Version: 7.0.0.2 (x64)
Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c
CPU threads: 4; OS:Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ja-JP (ja_JP); UI: ja-JP
Calc: CL
Comment 4 himajin100000 2020-07-28 01:12:56 UTC
Reproduced. (Crash reporter did not appear, though)

I don't know what's the cause of this bug, but the log says

OSL_ASSERT: pWindow

at 

https://opengrok.libreoffice.org/xref/core/svtools/source/control/toolbarmenu.cxx?r=a16e6122#57

after the previous assert, the following line is giving a message.

https://opengrok.libreoffice.org/xref/core/sw/source/core/layout/newfrm.cxx?r=b6ad72a3#313
Comment 5 himajin100000 2020-07-29 22:06:15 UTC
FYI:

before the second "OSL_ASSERT : pWindow" in the log file, the following message is given.

info:vcl.gdi.wndproc:34264:18032:vcl/win/app/salinst.cxx:573: SalComWndProc(nMsg=1139, wParam=0, lParam=2350370393376); inSendMsg: 0
info:vcl.gdi.wndproc:34264:18032:vcl/win/app/salinst.cxx:573: SalComWndProc(nMsg=1145, wParam=18024606, lParam=-721343405); inSendMsg: 0
Comment 6 QA Administrators 2022-07-30 03:41:05 UTC
Dear sawakaze,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug