So, I went back to bug 645273, and I'd have to say that it describes a different problem altogether. That problem dealt with reports not rendering in Windows. The implication in all of the comments there is that program was functioning but not producing data. That's different from the program hanging altogether. I will note also that none of those comments mentioned render times as an issue, so I think it's time to move away from that bug (and its age) in this discussion. It's not applicable here. Bug 790789 seems a more likely contributor.
Lengthy render times are an issue in many of the reports, and I believe that there are many people who would like to see the reports systems improved significantly. That being said, it does seem problematic that Gnucash would act as if it were hung if the program is simply rendering a report slowly. A user should be able to cancel a report request at any point in the process without getting a Windows notice that the program has stopped responding. I'll note that on the Mac, the process is unresponsive until the report finishes, which is only marginally better than the OS reporting the same. David On February 11, 2018, at 6:23 AM, doncram <donc...@gmail.com> wrote: If there's no functional bug, then there's a different bug: what is displayed should be changed to show "report processing...please allow a few minutes" or something like that. Surely it should not take seven years to change what a message states. --doncram On Sat, Feb 10, 2018 at 5:32 PM, Ken Pyzik <py...@cox.net> wrote: > Stan -- I am using 2.6.19 on 64-bit Windows 10. While the reporting module > is indeed very slow (bug report already out there was this) and while it > does say "Not Responding", eventually the report does come up (after about > 60-90 seconds). > > I agree that it may be way too long -- but it does technically work. My > belief is that it should work for you if given enough time. > > That all being said -- for almost of us -- this is still considered a bug > -- > but it does work -- eventually. > > -----Original Message----- > From: gnucash-user [mailto:gnucash-user-bounces+pyz01=cox....@gnucash.org] > On Behalf Of Stan Brown > Sent: Saturday, February 10, 2018 7:38 AM > To: gnucash-user@gnucash.org > Subject: Reports crash Gnucash > > MODERATORS -- The entire list doesn't need to see this, but I'd appreciate > if you'd pass this on to the developers. > > I wanted to like Gnucash, I really did, but it crashes e=whenever I try to > generate any report from any Gnucash file. > > I installed Gnucash 2.6.19 (from link at Gnucash.org) on my 64-bit Windows > 7 > laptop and 64-bit Windows 8 laptop and started working my way through the > tutorial. When I made a scheduled transaction and couldn't see it in the > ledger, I attempted to display the report of scheduled transactions. Got > only a blank window, and when I clicked Close the title bar showed "not > responding". When I clicked the red x in the upper right corner to close > the > window, I got "Gnucash has stopped working". > The same thing happened with every report I tried (maybe ten of them, min > various categories), and whether I had reports opening in a separate window > or not. This happens on both my laptops. > > I looked in the FAQ Wiki > https://wiki.gnucash.org/wiki/FAQ#Q:_I_cannot_get_any_ > report_to_display_not_ > even_the_sample_reports._All_that_displays_is_an_empty_tab. > and found a recommendation to change Internet options. That didn't help. > > I followed the link from the FAQ to the bug report > https://bugzilla.gnome.org/show_bug.cgi?id=645273 > which was entered SEVEN YEARS AGO. There were various suggestions related > to > Internet Explorer, which I tried, but as other folks found, those > suggestions did not help. > > I then Googled the gnucash-user archive and found nothing new, just > rehashes > of the same problem. > > HTML files and trace files were generated in my temp folder, but there's no > point in sending them since many others have done that already, yet the bug > remains unfixed. > > I've already wasted about six hours trying unsuccessfully to work around > the > bug, and several times that on the tutorial. I wanted to like Gnucash, and > I > know the software is free, but without the ability to produce any reports > it's worth even less than I paid for it. > > Extremely disappointing. > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
