Bug 104148 - Crash in: SwEditWin::TimerHandler(Timer *)
Summary: Crash in: SwEditWin::TimerHandler(Timer *)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.2.3.1 rc
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace, regression
Depends on:
Blocks:
 
Reported: 2016-11-24 18:04 UTC by Hans Gerstenkorn
Modified: 2017-02-04 09:38 UTC (History)
5 users (show)

See Also:
Crash report or crash signature: ["SwEditWin::TimerHandler(Timer *)"]


Attachments
Screen video from the bug (3.42 MB, video/mp4)
2016-11-28 11:30 UTC, Hans Gerstenkorn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hans Gerstenkorn 2016-11-24 18:04:43 UTC
This bug was filed from the crash reporting server and is br-63502341-f9c1-4553-8e42-c70158fde9e7.
=========================================

LO Version: 5.2.3.1, OS Microsoft Windows 10 Pro, Version 10.0.14393 Build 14393, Lenovo ThinkPad T430
----------------------------------------------------
Query copied, changed, form called, tables deleted, new inserted!
Comment 1 Alex Thurgood 2016-11-25 09:05:11 UTC
@Hans : can you be more specific as to the sequence of events that lead to this crash ?

From the trace alone, I can only hasard a guess that a grid redraw operation timed out somewhere, possibly because you scrolled with the mouse or expanded the window frame containing the grid, but at present from your summary description, I can't tell in which part of Base this occurred.
Comment 2 Hans Gerstenkorn 2016-11-25 15:01:43 UTC
Hi Alex, I attached a copy of the database to the bug report No 103926. Please see all comments especially Yours there. Thank You :-) hans
Comment 3 MM 2016-11-27 19:01:26 UTC
If it's not the same bug as in bug 103926, could you still supply a 'steps to reproduce' from scratch, so that it makes it a lot easier for us to reproduce. It's not good pointing to other reports and let ppl find out for themselfs if they can reproduce it or not. Not enough data usually means, the report will be INVALID.
Comment 4 Hans Gerstenkorn 2016-11-28 11:30:28 UTC
Created attachment 129072 [details]
Screen video from the bug
Comment 5 Hans Gerstenkorn 2016-11-28 11:34:18 UTC
Hi MM
I t'll try to give more details, so I could reproduce ow it comes to a crash - so I've made a creen-video and for better documentation please see bug No. 104148.
Comment 6 Hans Gerstenkorn 2016-11-28 11:36:10 UTC
This crash report is the result of reproducible processes, the bug persits also after Update to LO 5.2.3.3 from today:

You'll see into the screen video:

1. click to open the form "Zaehlerwerte_Wasser_Eingeben"
2. a little moment than the form was opened.
3. close the form
4. open the same form to edit
5. crash!
reproducable....
Comment 7 Alex Thurgood 2016-11-28 12:42:30 UTC
No repro for me on

Version: 5.2.3.3
Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf
Threads CPU : 8; Version de l'OS :Mac OS X 10.12.1; UI Render : par défaut; 
Locale : fr-FR (fr_FR.UTF-8); Calc: group

so this is a Windows-only bug, I guess.
Comment 8 Alex Thurgood 2016-11-28 12:48:06 UTC
Set to new as we now have backtrace and steps to reproduce.
Comment 9 Xisco Faulí 2016-12-01 15:03:39 UTC
Even though we have a backtrace and steps to reproduce it, someone needs to confirm it before moving it to NEW
Comment 10 Buovjaga 2016-12-07 17:35:10 UTC
(In reply to Hans Gerstenkorn from comment #6)
> This crash report is the result of reproducible processes, the bug persits
> also after Update to LO 5.2.3.3 from today:
> 
> You'll see into the screen video:
> 
> 1. click to open the form "Zaehlerwerte_Wasser_Eingeben"
> 2. a little moment than the form was opened.
> 3. close the form
> 4. open the same form to edit
> 5. crash!
> reproducable....

No crash on Win 10 with attachment 129006 [details]

Version: 5.4.0.0.alpha0+
Build ID: babf6d5e53516e80e8e3f2485796ebfaeb20e9c1
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2016-12-02_00:57:58
Locale: fi-FI (fi_FI); Calc: group
Comment 11 Terrence Enger 2016-12-08 16:24:30 UTC
I have failed to reproduce with Windows Vista 32-bit and
bibisect-win32-5.3 version (line rewrapped) ...

    Version: 5.3.0.0.alpha1+
    Build ID: 90646b4966c73637ddf592acd05b3091fb3fa41f
    CPU Threads: 2; OS Version: Windows 6.0; UI Render: default;
        Layout Engine: new; 
    Locale: en-CA (en_CA); Calc: group

which was committed to master 2016-11-17.
Comment 12 FrankS 2017-02-03 21:26:14 UTC
Unable to reproduce on Windows 10 64-bit.

Version: 5.3.0.3 (x64)
Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Layout Engine: new; 
Locale: en-GB (en_GB); Calc: group
Comment 13 Xisco Faulí 2017-02-03 22:50:28 UTC Comment hidden (obsolete)
Comment 14 Hans Gerstenkorn 2017-02-04 09:23:53 UTC
Hi Cisco,
the bug has disappeared in both (anonymous attachment and current local operating system) databases. At the moment my database has no bug! In use:

LO: Version: 5.3.0.3
Build-ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
CPU-Threads: 4; BS-Version: Windows 6.2; UI-Render: Standard; Layout-Engine: neu; 
Aerea scheme: de-DE (de_DE); Calc: group

Microsoft Windows 10 Pro 64; Version 10.0.14393 Build 14393; Lenovo T430s and same System at DELL Vostro.