|
By Przytula - Wednesday, July 12, 2017
|
Trying to generate online report as I did many times with latest version 3.0.1.0 on windows 10 proI starts to generate pages : but at 2510 of 6700 it always stops and get windows message : genopro has stopped working.... tried multiple times and same error produced also when trying to generate on local disk - see screenshot can we find any specific log/trace to identify the poroblem best regards, Guy Przytula 
|
|
By GenoProSupport - Thursday, July 13, 2017
|
|
Can you please send a sample .gno file to support at genopro dot com which causes the crash and I will investigate.
|
|
By GenoProSupport - Monday, July 17, 2017
|
We have been investigating the bug and our conclusion is the following: there is a memory leak in the VBScript Engine of Windows 10. When we run the report generator under Windows 7, the memory commit size is around 93 MB and remains stable during the whole time. When running the same report under Windows 10, the memory commit size jumps by several MB every second.
 Remember: GenoPro 2016 is a 32 bit application which can only access 4 GB (4,000 MB) of memory. It does not matter if your machine has more than 4 GB of RAM because the 32 bit application cannot access the rest. We are looking around for a solution... my guess is it will not be easy as Microsoft is abandoning VBScript and we are working full time on GenoProX which will use JavaScript for the report generator. Fixing a memory leak in a scripting host made by Microsoft may be an impossible task for us. One temporary solution is to run your report generator with an older version of GenoPro. As far as I aware, there is no memory leaks running GenoPro 2016 on the following platforms: Windows 98, Windows 2000, Windows XP, Windows 7, Windows Vista and all server versions of Windows.
|
|
By Przytula - Thursday, July 20, 2017
|
as the report can not be generated anymore :where can we download this older version - can we install it next to the current version ? thanks for all update best regards, Guy
|
|
By GenoProSupport - Friday, July 21, 2017
|
You are welcome to try an older version at https://www.genopro.com/archives/
However the problem is with Windows 10 having a memory leak in its VBScript Engine
|
|
By Przytula - Saturday, July 22, 2017
|
this problem only occurred recently - would it be possible to downgrade vb ?is vb part of ms c++ package - this has been updated recently is vb part of O/S or manually installed ? same problem with older version of genopro - memory increasing and crash best regards, Guy
|
|
By genome - Sunday, July 23, 2017
|
VB, or Visual Basic, is different from VBScript. The latter is installed as part of the OS. On my copy of Windows 10 I noticed that vbscript.dll had been updated on 11/07/17. I don't know how recently your problem started, but this update to vbscript.dll occurred as part of Windows Update 'Security Update for Microsoft Windows (KB4025339). If you have this update it might be worth uninstalling it via Windows Update to roll back vbscript.dll.
The problem does not occur on my .gno so unable to test if this is a solution. Alternatively you might like to try the attached individual.htm template by dropping into your Narrative Common\Code folder to replace the existing version. This version has been amended to free up objects when no longer required in an attempt to minimise memory usage.
|
|
By Przytula - Monday, July 24, 2017
|
removed the security update - boot - same probleminstalled the individual.htm instead of the existing : the memory still increases - but after handling the individual template the generate report does not continue 2232 files of 6000 and stoppped - no crash final report not displayed
|
|
By genome - Tuesday, July 25, 2017
|
Hmm, not sure what is happening, does the memory increase steadily throughout or just at the failure point? If the latter then maybe its due to a particular record casing a loop in the script.
I used your .gno from familytrees and it generated successfully under Windows 10 Home 64bit using just 66Mb of ram and also on Windows 10 Home 32bit where is used a mere 30mb of ram. Does that .gno still fail for you?
|
|
By Przytula - Tuesday, July 25, 2017
|
i opened the backup file dated 12/7same problem memory increases to 3800mb and crash i have windows 10 pro
|
|
By genome - Tuesday, July 25, 2017
|
So it appears that it works ok on some versions/copies of Windows 10 but not yours or GenoProSupport's. So it is probabably down to Microsoft to provide a solution 
Are you able to try the same report on a different version of Windows, e.g. Windows 8 as GenoSupport indicated? (I'm sure he meant to say 'older version of Windows' and not 'older version of GenoPro')
|
|
By Przytula - Tuesday, July 25, 2017
|
sorry, I have only 1 pcso it means I payed a license, but can not use the product anymore ? you indicated, you could reproduce the problem. Is it not possible to debug on that machine and find a solution ?
|
|
By appleshaw - Wednesday, July 26, 2017
|
If the problem is MS10 then try something else.
Possible options are install Linux and use GenoPro under wine. Not sure if reporting works there.
What is possible is to put GenoPro on a memory stick along with the skins folder and use another computer. You obviously need to point the report writer to the skins folder on the memory stick. I tried this at our local library and got into the report generator which then sat looking at a .js file, so perhaps something is needed there. However it works on our XP laptop.
Final thought, do what I did and ditch MS10
This is not a GenoPro fault but an MS 'feature'
|
|
By Przytula - Thursday, July 27, 2017
|
I totally do not agree with thisif your software uses software from other manuf you should guarantee that your program runs on different versions and other levels why would I need to install linux on my machine (I already have ubuntu in vmware machine) why would I need to buy a second pc to run this soft if a bug is detected in a licensed soft, the provider should be able to correct this or change his soft, that it always runs if I had known all of this, it might not have bought this soft and I already paid for the next coming version all my soft is current and supported as thousands other pc.. you as software provider should make contact with ms if you believe this is a bug in their soft
|
|
By appleshaw - Thursday, July 27, 2017
|
Apologies if my attempts to suggest options has upset you - I have no connection with GenoPro except as a fellow user. Looking at this series of messages I still think you are wrong to blame GenoPro when MS decides to change the way that VBScript behaves under Windows 10. If it upsets enough programs they may revert to an alternative. You get the impression that big companies think everyone has a machine with massive resources and if they have not got that then they are not important.
Back to the present situation. My initial thoughts were that this is a reporting problem but that this is not an everyday task. That is my experience but possibly not yours.
If report generation is an occasional activity then a more complicated procedure is acceptable. As you have Ubuntu then you can run GenoPro under wine. When I tried this on my Asus netbook some years ago the reporting did not work but I believe it is now possible.
I did not suggest you need to buy another PC, just a memory stick to contain the GenoPro software and gno file. I do know that you can then run a report on a borrowed machine; our local libraries provide this facility although thankfully they have not upgraded to Windows10.
I see you have also invested in the upcoming version which moves away from dependence on Microsoft routines and so hopefully will not run into this sort of problem in future.
|
|
By genome - Friday, July 28, 2017
|
Przytula
if your software uses software from other manuf you should guarantee that your program runs on different versions and other levels |
I cannot see how any software supplier can guarantee that their product will function correctly under all future versions of its OS platform, any more than Microsoft can guarantee that its OS versions will be backwards compatible will all other products running under it,GenoPro has been in existence for almost 20 years running on all Windows version from Windows 95 upwards and in my opinion in all that time shown a strong commitment to supporting its users.It can also be argued that the failing software, i.e. the Narrative Report, is not actually part of the licensed product. GenoPro provides the Report Generator allowing its customers to produce custom reports from their data. Almost all of the available reports have been produced and maintained by myself using the Report Generator with contributions and language translations from other users and as far as I am concerned can be considered to be open source 'freeware'. Prior to GenoPro 2016 all reports were largely distributed via updates on the Support Forum. Many users had difficulty in finding, downloading and installing these reports. I therefore requested that the reports be made available via the GenoPro 2016 download and update mechanism as a service to GenoPro customers and supplied GenoPro with the required files and updates as required.I have an interest in genealogy and also enjoying scripting as a hobby during retirement from full time employment and have supported users of these reports for over 12 years and hope to continue to do so.
I am keen to resolve your current problem with the Narrative Report but at present able unable to reproduce the problem on either of the Windows 10 PCs available to me. It may be of assistance if you can say when the rapid memory increase starts, is it throughout the report generation or only when a particular template is started e.g. code\individual.htm? Also do you notice increase in ram (e.g. above say 100Mb) when a report is generated from other .gno files, e.g. Harry Potter sample? I will consider upgrading one my PCs to Windows 10 Pro but would also like to know if any other Windows 10 Pro users experience this issue. If the problem cannot be easily solved (e.g. we need Microsoft to provide a solution) then perhaps circumvention could be considered. Since earlier versions of Windows appear to be unaffected then running say Windows XP in a virtual machine under Windows 10 Pro may work.
|
|
By Przytula - Friday, July 28, 2017
|
thanks for all replyno at the start of generate report : it already uses 100mb of memory and keeps increasing individual.htm is the longest part and makes it crash I tried another tree with less individuals and it that case it also increases in memory use, but ends as the nbr of individuals is much smaller : total mem used 680Mb best regards, Guy
|
|
By genome - Friday, July 28, 2017
|
We are not alone with this issue https://stackoverflow.com/questions/45274885/vbscript-consumes-memory-after-creators-update-win-10-64bit
M$ have messed up again big time!
Just spent over 4 hours 'upgrading' my Windows 10 Home 64bit with Creators Update and guess what? , I now have the out of memory problem when trying to generate a Narrative Report!.It looks like you have two choices, either uninstall the Windows 10 Creators Update (Google it if not sure how) but NOT recommended. Or wait for MS to realise the error of their ways and provide a fix.
|
|
By appleshaw - Friday, July 28, 2017
|
Is there a third, temporary, option? Does a wine version use the Win10 VBScriptor or can it use a 'working' version. If so can a wine GenoPro now generate reports?
|
|
By genome - Saturday, July 29, 2017
|
Well after joining Microsoft's Windows Insider Program and spending another 3 or 4 hours applying the latest preview from the Fast Ring i.e.Windows Version 1703 (OS Build 16241.1001) I can confirm this bug has been fixed by Microsoft!
Will eventually get rolled out more generally at some point I guess.
|
|
By rkuhmann - Monday, August 7, 2017
|
Am (likewise) experiencing report generation CRASHES with error msg [below] ...when compiling a build of my GNO (27,250 names) --> HTML for FTP upload to my private website. It's failing on Win 10 Enterprise, 64-bits, current version (Phenom Quad-core, 8-GigaB RAM, 2-TeraB HDD) & under Windows 7 Enterprise, 64-bits, current version (Intel I7, 8-GigaB RAM, 1-TeraB HDD). Am using 2016 version 3.0.1.0 GenoPro, with (EN) Narrative Report 2016-07-16. Various "tags" are red-flagged as errors - but I am not even using those tags. The failures began after my last successful "build" of 2017-07-20 c.f. [link]:
http://www.kuhmann.com/Genealogy/default.htm
Shall attempt a "build" under 32-bit Windows 10 Enterprise, current version (installed to a 64-bit CPU computer, AMD Athlon x2, 4-GigaB's).
|
|
By genome - Monday, August 7, 2017
|
I am surprised to see that you are getting this failure when running it under Windows 7 as well as Windows 10 as my testing indicated it was caused by Windows 10 Creators Update.
If it is the same problem then the memory leak will occur with almost any .gno such as the Harry Potter sample, although RAM may not be completely exhausted. You should see memory for GenoPro.exe increasing steadily when monitored e.g. with Task Manager. Can you still generate from your .gno dated 20.7.17 ? If so maybe we need to look at updates to it since then.
|
|
By Przytula - Wednesday, September 27, 2017
|
any new progress on this ?I still cannot generate reports.. no work-around ? all help welcome best regards, Guy
|
|
By genome - Wednesday, September 27, 2017
|
Well I'm pinning my hopes on the imminent Windows 10 Fall Creators Update, due to be released around 17th October. This will will bring the general release build version, currently 16299, beyond that of the working Insider Program Fast Ring release I tested against earlier (16241) so hopefully it will still have the patch that fixes the problem. However I have still not come across an official Microsoft notification of this Scripting bug.
A note of caution that if you also get this problem with earlier versions of Windows, i.e. before original Windows 10 Creators Update or earlier versions of Windows (8,7, etc) then it may not be the same issue. So if you get the failure under Windows 7 say, then if you can get a copy of your .gno to me then I will try to look into it further.
|
|
By genome - Tuesday, October 17, 2017
|
Yay! Its 17th October and MS has delivered the Windows 10 Fall Creators Update (Os version 1709 Build 16299.15) to my laptop.
And guess what it DOES FIX this issue (for me anyhow). A report for some 3500 individuals and 1050 families peaked at about 72Mb Ram usage. Why oh why could they not have put out a hotfix for this earlier.
|
|
By maru-san - Wednesday, October 18, 2017
|
Thanks, Ron, for this hint.
Have downloaded it and it solved my problem with creating the big Gedom file, although I had stripped down my file of non essential data by app 25%.
|
|
By Przytula - Sunday, October 29, 2017
|
yes, I also downloaded the windows update and yes, the problem is corrected
thanks for all help
best regards, Guy Przytula
|