Page 1 of 1

Show Project Statistics v2.5 on V7 failed to complete

Posted: 01 Jun 2021 10:06
by paultt
@Mike,
Tried the Show Project Statistics plugin this morning after downloading and installing. Did not change any options, just clicked Run. It got to 77% after 7 minutes, and then it did not progress any further over then next 25 minutes, so had to 'kill' FH via Task manager.
ShowProjectStats2.5.jpg
ShowProjectStats2.5.jpg (68.01 KiB) Viewed 1488 times
FH v 7.0.5 with :
Record Counts...
Individual Records:175552
Family Records: 58985
Note Records: 615
Source Records: 4013
Repository Records: 105
Submitter Records: 3
Submission Records: 0
Media Records: 8494
Place Records: 18905

on Windows 10 Pro 64-bit operating system, x64-based processor version 20H2 and 8gb memory

Is my project too big for the plugin?

Re: Show Project Statistics v2.5 on V7 failed to complete

Posted: 01 Jun 2021 10:22
by tatewise
Sorry Paul. That is certainly a large Project. However, the plugin should cope.
A clue to the problem is that it says (Not Responding).
That is indicative of what is happening with plugin after plugin in FH v7 that did not happen in FH v6.
The Lua 5.3 interpreter garbage memory management seems not to work as well as it did in Lua 5.1 for some reason.
So I have been progressively adding garbage memory management commands into my plugins to overcome the problem that usually only comes to light with large Projects.
You may have noticed similar postings in this Forum regarding (Not Responding) and memory management for other plugins.
Let me investigate possible adjustments for you to try...

The attached Show Project Statistics plugin Version 2.5.1 Date 01 Jun 2021 hopefully solves the problem.

Re: Show Project Statistics v2.5 on V7 failed to complete

Posted: 01 Jun 2021 11:50
by paultt
@Mike,
That seems to have solved the issue! It ran for just under 2 minutes before completing and giving a result. Now to spend time analysing....
Many Thanks

Paul TT

Re: Show Project Statistics v2.5 on V7 failed to complete

Posted: 01 Jun 2021 14:30
by tatewise
Excellent. That fix will be in the next published version.