LO Ver 7.0.6.2 (x64) under Windows 10 Ver 20H2 crashes repeatedly at the same point

I’m working on my ninth decade here. I’ve been playing with computers since a class project when we wrote an assembler for the brand new IBM 1401. I learned COBOL directly from Grace Hoppe and worked in FORTRAN and the original IBM ISAM when they came out. I’m older than dirt. I’m running Windows 10 Pro Ver 20H2 build 19042.985 on a Dell 7010 with an Intel 3.4 GHz i5-3570, 16 GB RAM, an internal 2 TB drive and 6 USB drives.

I’m evaluating LO-BASE for potential use writing databases for public charities. I’m following the video tutorials provided by TheFrugalComputerGuy.com. LO BASE crashes every time at a certain point in his “Home Invoice” tutorial which begins at Video 73 where he defines three tables, Customers, Invoice, and Tasks and links them via ID fields, then in Video 74 he defines two forms, Customers and Invoice. The Customers form works. In the Invoice form he uses the form wizard to define a subform with 5 fields and a main form with 5 fields.

In the Invoice main form he defines a VARCHAR field named Status. When the form is complete he goes back and modifies the Status field making its display box wider and changing it to a List Box with bounds of “0”;“1”. Then, at 6 minutes in the video, he attempts to modify the CustomerID by changing it into a List Box, with the content type set to SQL, then he clicks on the “…” icon next to List content and attempts to link it to the Customer table on the CustomerID field.

At this point my installation of LO crashes repeatedly. I rebuild the data files then restart and it crashes again. During data rebuild it displays a blank LO WRITER box which can’t be closed with the “X”. I had to end LO in the Task Manager.

After several crashes I removed the entire LO program and re-installed it from a new download of LibreOffice_7.0.6_Win_x64.msi. The problem continues after the re-installation.

I submitted two crash reports to BugZilla.
crashreport.libreoffice.org/stats/crash_details/aeacefb6-e997-493d-9596-664a71ede7bc
and
crashreport.libreoffice.org/stats/crash_details/c921ab97-e791-425d-9433-9a6c7f8ccf10

What’s up? Is this a known issue? What is particularly disturbing is the appearance of the completely blank and unresonsive LO-WRITER screen after the rebuilding routine. When this screen is up the Start button and task bar is not visible so I can’t start Task Manager with the mouse or by typing in a Run box. I had to hit the hardware override Ctrl-Alt-Delete to bring up Task Manager and terminate LO completely. Then LO would insist on rebuilding the last know data file again which would bring up the unresponsive WRITER screen again. I found a leftover Invoice.odb.lck file in my working directory, H:!!GrInv. I found that I had to delete the .lck file after using Task Manager to terminate LO … then LO would start.

If you go through the tutorial and it works I would like to know about it.

Paul in NY

Hello,

Did not crash as you have but using a newer LO version:

Version: 7.1.2.2 (x64) / LibreOffice Community
Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Now did have a rendering problem at the same point where you crashed and this may be your problem.

From the menu choose Tools->Options. Then under LibreOffice->View in the upper right corner of the right hand panel under Graphics Output, insure no selection for Use Skia for all rendering.

Then you need to select OK button and close all open LibreOffice items. Start the Base file and see if crash is fixed.

@Ratslinger … Hi, should I up grade to the newer 7.1.2.2 first, or should I just disable Skia first? I just checked and Skia IS currently enabled. I know that Skia is a 2D rendering engine owned by Google used to paint the screen in Chrome and Android. If Skia is disabled what does LO use in its place? Paul in NY.

I would disable Skia first. Not certain (gave up on Windows some time ago - Linux now) but quite often have seen this as a LO issue in windows.

Not certain changing LO versions will help (might). Using v7.1.4.2 on Linux Ubuntu currently.

Hi again. I disabled Skia and worked my way through the tutorial to the point where, after setting content type to SQL, I click on the “…” icon and it crashes instantly. It then attempts to recover the files, but a blank box appears with no title bar contents. When I attempt to close this box with the “X” it is not responsive. Task Manager reports that LO is not responding and I end the process.
Should I now install the newer 7.1.4 LO? The version you are running, 7.1.2.2 is not shown on the download page. Should I manually remove the old LO before installing the new one?
Paul in NY

@Paul_L,

I would first try resetting the user profile. For that see this page → LibreOffice user profile

If that does resolve the issue, then use Windows to uninstall LO. I personally always use the latest version (behind a bit on Windows) but if you want any older version, there is an archive link near the bottom of the download page.

It’s me again. After the crash LO left behind an Invoice.lck file. I attempted to restart LO without installing the newer version. I told it to rebuild the user profile to the last known good condition. It went through two rebuilding processes and finally restarted. I terminated LO. The Invoice.lck file is still there. What’s up???

Should be able to delete the .lck file without losing anything.

@Ratslinger … I reset the user profile but I did not install the newer 7.1.2.2 available version so I’m still running 7.0.6. When I change the CustomerID field to be a List box with SQL content and click on the “…” icon it properly displays the available tables and permits me to select the CustomerID and Name fields from the Client table returning SELECT “NAME”, “CLIENTID” FROM “CLIENT” which is correct. So … it doesn’t crash and seems to be working but I haven’t run the code yet, and I don’t really know what I did to fix it. I guess it was something in the user profile. Thanks for helping. Paul in NY

@Paul_L,

Resetting a user profile can cure many problems. Unfortunately this does not actually indicate what problems were corrected. Just accept that it is now working.