I tried to replicate the bug with the following steps:

1. Open the attached document in Open Office Writer
2. Click in the space between the last and next to last table
3. Hit return a few times (3-5 times)
4. Observe that nothing has crashed
5. Keep hitting the return (20-50 times)

I have passed through those steps three times:
1. Using only main Enter key
2. Using only num-pad Enter key
3. Using mix of 1st and 2nd

I tried hitting Enter, as well as keeping it pressed.

I deviated from the original stems given by treshall@yahoo.com  and repeated the same passes clicking in the space between several different pairs of tables in the attached file -- nothing crashed.

I also created a new 6 page document filled with tables and repeated all of the above -- nothing crashed.

I was unable to replicate this issue.

---

Tested first with Russian (the default on my system) locale set in both Windows 7 and OpenOffice and then with English set in both.
OpenOffice's locale was changed to English in Tools -> Options -> Language Settings -> Languages -> Locale setting.

System: Windows 7 64bit (Russian & English locales), clean install of Apache OpenOffice 4.1.1 (Build: 9775, rev: 1617669, build date: 2014-08-13) Russian & English locales.

I could replicate this bug on my system (OO 4.1.1 + Windows 8.1, both English).
I followed the steps bellow:

1.  Opened the document attached;
2.  Clicked in the space between the last and next to last table;
3.  Kept pressing return and observing Writer’s response;
4.  After pressing it 50 times, the program crashed.

It’s important to mention that pressing return 50 times puts enough space to make the table to go the next page, creating a completely blank page before continuing the table. The error occurs also if I click on the space between other tables, not just the last and the next to last ones. I would recommend checking how Writer manager this blank page in between.

I've attempted to reproduce this issue while following exactly the steps from each comment above with no success.

Some extra tests that I've tried included:
1. Using tabs to create space rather than entering in new lines via "Return" or "Enter" keys
2. Adding more tables to the attached document before following reproduction steps
3. Using various font sizes before hitting "Return" and "Enter" keys
4. Using increased line spacing (between 0.00" and 2.58")
5. Pressing and holding "Return" and "Enter" keys
6. Increasing the number of pages in the attached document to 502 via steps that mention adding new lines via "Return" or "Enter" keys

Note: I've also tried this on Mac OSX 10.9.5 with the same results.

System: Windows 7 64-bit (English locale - Mac OSX Boot Camp partition)
Apache OpenOffice 4.1.1 (Build: 9775 - Rev. 1617669 - 2013-08-13)

AOO411m4(Build:9774)  -  Rev. 1614269 en-us
Windows 7 Professional SP-1 64-bit

I opened the document, clicked at the bottom of Page 8 (cien | one hundred). There is a blank line between this table and the table on the next page. I then pressed return lots of times, ultimately making the document 92 pages long, no crash. Most pages are blank with only one blank line. I moved my cursor onto one and pressed <Enter> many times on that page, creating a page with blank lines. No crash.

I moved the cursor back to page 5, placing it on the line between "Other useful words" and the start of the Table (Spanish | English). Press the <Enter> key many times (more than 50), hold down the <Enter> key. I now have 5 blank pages before the start of the table. No crash

(In reply to treshall from comment #0)
> Created attachment 83897 [details]
> odt writer document for which the crash occurs
> 
> 1.  Create a document with multiple tables.  (can be as few as 5 pages long)
> 2.  Click in the space between the last and next to last table.
> 3.  Hit return a few times (3-5 times).
> 4.  the program crashes.
> 
> attached is a document in which this occurs.

This sounds similar to bug 125722, bug 125971 and 126043. But I cannot reproduce it. To be sure, that it is not a problem with the amount of tables, please try it with one table as described in bug 125971.

(In reply to Regina Henschel from comment #5)
> (In reply to treshall from comment #0)
> > Created attachment 83897 [details]
> > odt writer document for which the crash occurs
> > 
> > 1.  Create a document with multiple tables.  (can be as few as 5 pages long)
> > 2.  Click in the space between the last and next to last table.
> > 3.  Hit return a few times (3-5 times).
> > 4.  the program crashes.
> > 
> > attached is a document in which this occurs.
> 
> This sounds similar to bug 125722, bug 125971 and 126043. But I cannot
> reproduce it. To be sure, that it is not a problem with the amount of
> tables, please try it with one table as described in bug 125971.

Have tried it again a couple of times, now I do not get a crash.  Not sure what is going on now...

System: AOO411m6 rev 1617669 en-US and AOO420 rev 1692551 en-US
        Windows 7 32-bit (All English Locale)

I tried to replicate the bug on both the version in which the bug occurred (4.1.1) and a later version (4.2.0) with the following steps:

1. Downloaded the file given by the original reporter - "otd writer document for which the crash occurs"
2. Opened OO
3. Opened the downloaded file
4. Clicked in the space between the last table and the next to last table
5. Tapped enter until the last table was on a new page, about 50 taps, no crash
6. Held enter down until the last table was on page 20, no crash
7. Clicked in the space between the "To Tell Time" table and the table before it
8. Tapped enter until the "To Tell Time" table was on a new page, no crash
9. Held enter down until the "To Tell Time" table was on page 6, no crash
10. Deleted all tables after the first table
11. Tapped enter until the first table was on a new page, no crash
12. Held enter until the first table was on page 7, no crash 

I incorporated testing the last table, a table in the middle of the document, and only one table while tapping enter to a new page or holding enter down until a new page like mentioned in the above comments. 

I was not able to replicate the bug on either version.

I was able to recreate this bug on a Windows 8.1 machine.  I entered comments on bug report Issue 125722 with steps to recreate and attachments.

I have gathered information from similar bugs, 125971, 126043 and 125722, and with the information also provided in previous comments I selected and performed the sets of tests presented below.
I had no success in reproducing the initial crash described in this bug or in any of the other mentioned bugs. 

The environment for these tests is a Windows 10 machine. The first set of tests was performed using OO version 4.1.1 followed by an upgrade to version 4.1.3.

1. Create MS Office (2016) document with multiple tables and open in OO to edit
1.1. Saved document as .docx
1.2 Closed document
1.3. Open OO Writer
1.4. Open MS Office doc
1.5. Moved the cursor before each table and pressed the Enter key until each table got on new page

2. Create New OO document with 2 tables and insert blank page between them
Table 1: 4x7, Don’t Split table
Table 2: 4x7, Don’t Split table
2.1. Place the cursor before second table
2.2. Insert Manual Break > Page  Break
2.3. Place the cursor before second table and keep the Enter key pressed until table moves to page 3
2.4. Place the cursor before first table and keep the Enter key pressed until table moves to page 2


3. Download OO doc attached by treshall@yahoo.com bug and used steps provided in first comment
3.1. Open the downloaded document in OO
3.2. Click in the space between the last and next to last table.
3.3.Hit return a few times (3-5 times).


I have changed AutoSave from 15 minutes to 1 minute and continued with next tests.


4. Create new OO doc with 2 tables and keep the Enter key pressed until AutoSave runs
Document with 2 tables and 2 empty lines between table
4.1. Place the cursor on the second empty line before the second table
4.2. Press the Enter key until AutoSave runs


5. Create one table and split table in 2
5.1. Insert table 2x20
5.2. Copied content from the document uploaded by treshall@yahoo.com in each column
5.3. Split table
5.4 Place cursor between the 2 tables and press the Enter key until the second one is moved to new page


6. Create new OO document and copy tables from the document uploaded by treshall@yahoo.com in the new document
6.1. Created new document
6.2. Opened the downloaded document and copied content
6.3. Added content to the new document
6.4. Placed cursor at the end of the document and hit the Enter key 7-9 times
6.5. Insert new table at the end
6.6. Copied content from the above table and pasted into the newly created table
6.7. Removed empty lines between the last 2 tables
6.8. Hit the Enter key 3 times to move the last table to new page


Upgraded OO to version 4.1.3


7. Opened to edit the last created document (in test 6) with the new version of OO
7.1. Place cursor before the second table in the document
7.2. Hit the Enter key to move the table to next page > 2 time
7.3. Now place the cursor under the first table to move the Heading “To say goodbye” on the second page > 4 times
7.4. Split the last table in 2 tables 
7.5. Place the cursor between the tables
7.6. Insert line break
7.7 Place cursor before line break
7.8. Hit the Enter keys until the last table moves to new page > 19 times

I have tried replicating this bug on the version in question (4.1.1) running on windows 7 64 bit home edition both English.
I tried replicating the bug using these steps:
1. downloaded and opened the attached .ODT file as specified.
2. place the cursor between the last and next to last table.
3. hit return multiple times.

Unfortunately, I was not able to replicate this bug using the above steps.

I tried multiple variations of these steps (e.g. higher number of return button presses; position the cursor in different places; and created my own .ODT with 30 tables replicating the same steps).
I was hoping that another variation may duplicate the bug you encountered but it was to no avail.

I wasn’t able to replicate this bug on Windows 10 Apache OpenOffice version 4.1.2 
The steps which I followed to replicate the bug are as follows.
1.	Downloaded the document used by the reporter for bug replication.
2.	Opened the document using OpenOffice writer.
3.	Scrolled down to the bottom of the document to reach the place as indicated by the reporter.
4.	After figuring out the location of the last two tables, the cursor was placed at that blank position.
•	“To ask for help” and “Other useful words” were the 2 tables.
•	The cursor was placed just before the words “Other useful words” was present.
•	Hitting the return key for some number of times shifted the position of the table to the subsequent pages.
5.	Hit the Enter (Return) key 50 times and couldn’t find any crash.
6.	The aesthetics of the document didn’t seem good now but there was no issue of crashing while doing the above steps.
I couldn’t replicate this bug on my computer. I also performed some extra tests which I did while trying to replicate this bug.
1.	Created a text document in OpenOffice Writer.
2.	Inserted many tables in the text document using 
•	Clicking the INSERT option on the Toolbar menu
•	Choose TABLE
•	Entered the total rows as 2 and total columns as 3 and clicked the create option.
        3.    Followed the same process (step 2) and created 10 tables.
        4.    Hitting the Enter key in the blank field between the 9th and the 10th table.
        5.    The enter key was continuously pressed for many times in order to replicate the bug reported.
Still couldn’t replicate the reported bug on my computer.

I was unable to replicate this bug, I've tried using the following steps:
1. Created a new document
2. Clicked in the document, did table->insert with 25 columns and 25 rows as the size. In the options part I left "Heading" and "Don't split table" unchecked, and left "Border" checked. Afterwards I clicked OK to finish inserting the table.
3. Repeated step 2 fifty times for a total of 51 tables with 51 total pages each having one page.
4. Went on page 50 to click in the space between the last and next to last table.
5. Pressed return 10 times

I observed no crash following the steps, and have also tried using the attached document and still could not replicate the bug.

Apache OpenOffice Build:
Apache OpenOffice 4.1.2
AOO412m3(Build:9782) - Rev. 1709699

Configuration:
Operating System: Windows 10 Pro 64-bit (10.0, Build 14393.693)

Unable to replicate issue on OpenOffice version 4.2.0 AOO420m1(Build:9800)  -  Rev. 1784055 Eng / US

OS: Windows 10 Pro 64 bit

Using the attached document, I was unable to reproduce any crash by moving any of the tables.

After approximately 20 pages of inserted lines between tables, still no errors.

Judging by the given steps to replicate, and comments, this bug may be similar to bug #126043

I presume someone here patched main/framework/source/services/autorecovery.cxx to refer people to this bug (125528) if they get the assertion there?

I got it in Base, in a debug build, by opening a saved database query, and leaving it open for a few minutes.

I had Java loaded, and it caught the exception below when I clicked "Cancel" on the dialog for this bug. Judging by the functions in the stack, it could be that some timer could be the problem? I'll attach a debugger and investigate the next time it happens.

Stack: [0x00007fffdffff000,0x00007ffffffff000],  sp=0x00007fffffff7fd0,  free space=524259k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [libtl.so+0x2eef7]  DbgFunc(unsigned short, void*)+0xaea
C  [libvcl.so+0x139b70]  psp::PrinterInfoManager::setupJobContextData(psp::JobData&)+0x8820
C  [libtl.so+0x2db90]  DbgOut(char const*, unsigned short, char const*, unsigned short)+0x29e
C  [libuno_sal.so.3+0x31afa]  unsigned __int128+0xba
C  [libfwk.so+0xf2a04]  char+0xc5e3
C  [libfwk.so+0xecaff]  char+0x66de
C  [libvcl.so+0x14b7a1]  Timer::ImplTimerCallbackProc(void)+0x8d
C  [libvclplug_gtk.so+0x24b89]  DeInitAtkBridge(void)+0xecbf
C  [libvclplug_gtk.so+0x24b22]  DeInitAtkBridge(void)+0xec58
C  [libglib-2.0.so.0+0x4ba27]  __float128+0x117
C  [libglib-2.0.so.0+0x4f458]  __float128+0x138
C  [libglib-2.0.so.0+0x4f794]  __float128+0x214
C  [libglib-2.0.so.0+0x4f824]  __float128+0x64
C  [libvclplug_gtk.so+0x24e8f]  DeInitAtkBridge(void)+0xefc5
C  [libvcl.so+0x1479c8]  Application::AppEvent(ApplicationEvent const&)+0xa8
C  [libvcl.so+0x145180]  Application::Execute(void)+0x2a
C  [libsofficeapp.so+0x26a86]  +0xe556
C  [libvcl.so+0x14a597]  VclResId(int)+0x2241
C  [libvcl.so+0x14b348]  SVMain(void)+0x1f
C  [libsofficeapp.so+0x703f8]  short+0x98
C  [soffice.bin+0x11d9]  unsigned long+0x49
C  [soffice.bin+0x11b7]  unsigned long+0x27
C  [soffice.bin+0x10af]  _start+0x16f

Got it again:

Stack trace:

Thread 23 (Thread 80d806400 (LWP 101095/soffice.bin)):
#0  0x0000000801d3fb1a in _poll () from /lib/libc.so.7
#1  0x0000000801a49d66 in pthread_suspend_all_np () from /lib/libthr.so.3
#2  0x000000080ef6d73d in g_main_context_pending () from /usr/local/lib/libglib-2.0.so.0
#3  0x000000080ef6d824 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0
#4  0x000000080dc24e8f in GtkXLib::Yield (this=0x80d8e4388, bWait=<value optimized out>, bHandleAllCurrentEvents=<value optimized out>)
    at /openoffice/trunk/main/vcl/unx/gtk/app/gtkdata.cxx:874
#5  0x00000008055479c8 in ImplYield (i_bWait=<value optimized out>, i_bAllEvents=false) at /openoffice/trunk/main/vcl/source/app/svapp.cxx:476
#6  0x00000008056f97a6 in Dialog::Execute (this=0x7fffffff8cd0) at /openoffice/trunk/main/vcl/source/window/dialog.cxx:701
#7  0x0000000805539a41 in SolarMessageBoxExecutor::doIt (this=<value optimized out>) at /openoffice/trunk/main/vcl/source/app/dbggui.cxx:1862
#8  0x00000008056e5ad4 in vcl::SolarThreadExecutor::impl_execute (this=0x7fffffff9058, _pTimeout=<value optimized out>) at /openoffice/trunk/main/vcl/source/helper/threadex.cxx:103
#9  0x0000000805539b4f in DbgPrintMsgBox (
    pLine=0x7fffffff90d0 "Error: May be you found the reason for bug #125528#. Please report a test scenario to the right developer. THX.\nFrom File /openoffice/trunk/main/framew"...)
    at /openoffice/trunk/main/vcl/source/app/dbggui.cxx:1899
#10 0x0000000804a2eb90 in DbgOut (pMsg=<value optimized out>, nDbgOut=<value optimized out>, pFile=<value optimized out>, nLine=<value optimized out>)
    at /openoffice/trunk/main/tools/source/debug/debug.cxx:1738
#11 0x0000000800a31afa in osl_assertFailedLine (pszFileName=0x80a7bbb1b "/openoffice/trunk/main/framework/source/services/autorecovery.cxx", nLine=1713, 
    pszMessage=0x80a7bbf5f "May be you found the reason for bug #125528#. Please report a test scenario to the right developer. THX.") at diagnose.c:263
#12 0x000000080a6f2a04 in framework::AutoRecovery::implts_timerExpired (this=<value optimized out>) at /openoffice/trunk/main/framework/source/services/autorecovery.cxx:1713
#13 0x000000080a6ecaff in framework::AutoRecovery::LinkStubimplts_timerExpired (pThis=0x81f86ed00, pCaller=0x6) at /openoffice/trunk/main/framework/source/services/autorecovery.cxx:1618
#14 0x000000080554b7a1 in Timer::ImplTimerCallbackProc () at /openoffice/trunk/main/vcl/source/app/timer.cxx:141
#15 0x000000080dc24b89 in GtkXLib::timeoutFn (data=0x80d8e4388) at /openoffice/trunk/main/vcl/unx/gtk/app/gtkdata.cxx:745
#16 0x000000080dc24b22 in call_timeoutFn (data=0x81f86ed00) at /openoffice/trunk/main/vcl/unx/gtk/app/gtkdata.cxx:725
#17 0x000000080ef69a27 in g_list_sort_with_data () from /usr/local/lib/libglib-2.0.so.0
#18 0x000000080ef6d458 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0
#19 0x000000080ef6d794 in g_main_context_pending () from /usr/local/lib/libglib-2.0.so.0
#20 0x000000080ef6d824 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0
#21 0x000000080dc24e8f in GtkXLib::Yield (this=0x80d8e4388, bWait=<value optimized out>, bHandleAllCurrentEvents=<value optimized out>)
    at /openoffice/trunk/main/vcl/unx/gtk/app/gtkdata.cxx:874
#22 0x00000008055479c8 in ImplYield (i_bWait=<value optimized out>, i_bAllEvents=false) at /openoffice/trunk/main/vcl/source/app/svapp.cxx:476
#23 0x0000000805545180 in Application::Execute () at /openoffice/trunk/main/vcl/source/app/svapp.cxx:510
#24 0x0000000800e66a86 in desktop::Desktop::Main (this=0x7fffffffe2d8) at app.cxx:2232
#25 0x000000080554a597 in ImplSVMain () at /openoffice/trunk/main/vcl/source/app/svmain.cxx:196
#26 0x000000080554b348 in SVMain () at /openoffice/trunk/main/vcl/source/app/svmain.cxx:237
#27 0x0000000800eb03f8 in soffice_main () at sofficemain.cxx:45
#28 0x00000000004011d9 in sal_main () at main.c:31
#29 0x00000000004011b7 in main (argc=1, argv=0x7fffffffe3d0) at main.c:30



Unfortunately, in frame 12, the exception caught isn't stored in any variable, so I cannot see what it is.

I believe that this time I reproduce it by opening a database query, then opening an unrelated new Writer document and typing something into it, and leaving it for a few minutes - maybe autosave needs to start running for this to happen?

I have this issue too. The crash seems to occur when the table gets moved from one page to another.

1. Create a text document
2. Create a table
3. Hit Enter until the table is pushed onto the next page
4. At this point, OpenOffice will crash.

OpenOffice Writer 4.1.4
Lenovo Yoga 720 running Windows 10 Home