GNOME Bugzilla – Bug 698094
Runtime Error! Crash, GUI closes with loss of data since the last save
Last modified: 2018-06-29 23:14:58 UTC
I have GnuCash installed on a Windows XP and a Windows Seven and both suffer from the same problem that comes to occur with a frequency of several per section, approximately one every five minutes. In the middle of my work GnuCash displays a message: "Runtime Error! Program: C:\Arquivos de programas\gnucash\bin\gnucash.exe The application has requested the Runtime to terminate it in an unusual way." and closes with total job loss since the last save. I tried to take a sreenshot but got a message saying there was no memory and was not possible. I have 1.5GB that normally working at 60%. I really like GnuCash and would not want to leave him. Is there any solution to this problem?
When I first went to install on my Windows XP, I received a box of languages selection, so far so good, but then I clicked on the dropdown to see other languages, the box suddenly closed. After that, every time I clicked the installer it showed the box of languages selection and quickly closed. I could no longer install by clicking on the installer then I went to DOS and ran the installer and without touching the dropdown language selection I clicked next and could follow the installation process to the end. So without touching the language selection and clicking next I could install in my Windows Seven as well.
Created attachment 241616 [details] Screenshot of Crash Message captured in Windows Seven Screenshot of Message in Windows Seven captured after a crash. Clicking "Aceptar" GnuCash GUI closes and all data is lost.
Can you check the content of the trace file please: http://wiki.gnucash.org/wiki/Tracefile
Thank you for the reply and sorry for the delay. (I lost a day here fighting with .NET 4.0, it seems okay now). Here is attached all tracefile I found here on WinXP (I have Windows Seven too if you need). Are twenty-eight files in total. If there is anything else I can help just let me know.
Created attachment 241767 [details] GnuCash Tracefiles WinXP Here is attached all tracefile I found here on WinXP. Are twenty-eight files in total.
(In reply to comment #6) > Thank you for the reply and sorry for the delay. (I lost a day here fighting > with .NET 4.0, it seems okay now). > > Here is attached all tracefile I found here on WinXP (I have Windows Seven too > if you need). Are twenty-eight files in total. > > If there is anything else I can help just let me know. Please disregard this comment (I could not remove it), there was an error in bugzilla Server: "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, bugmaster@gnome.org and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log."
Your trace files show several different errors. The last series of trace files all contain this error: * 17:38:16 CRIT <GLib> g_date_compare: assertion `g_date_valid (lhs)' failed Gnucash complains about an invalid date somewhere. I'm not sure where that comes from though. Before that, you have several trace files with gdk errors: * 14:19:39 WARN <Gdk> gdkcursor-win32.c:131: CreateCursor failed: A operação foi concluída com êxito. * 14:19:39 WARN <Gdk> gdk_cursor_new_for_display: no cursor 108 found (repeated many times, followed by one:) * 14:19:39 WARN <Gdk> gdkpixmap-win32.c:279: CreateDIBSection failed: Parâmetro incorreto. I'm afraid I don't understand at all what happens on your machines. I haven't seen this behaviour anywhere else. Can you install gnucash 2.4.11 ? Does it show the same strange behaviour ?
Yes, of course. I had thought to install a previous version for testing. I will do this to eliminate some variables. Add the information I have GnuCash Portable version 2.4.11 and it also presented some Crash on my WinXP so it I did not do yet. How Gnucash came LINUX I thought it might be problems with the GUI for Windows. To see if there is any behavior and / or errors change I changed the Gnucash theme. This is now also more beautiful :) Until now there was no crash. I want to test it some more time. I'll need some time to test because I do not use Gnucash every day just when I update data. Remember what I told you: I have two completely separate systems, one WinXP and Win7 and both have the same problem. I'll attach the Win7 tracefiles. In my opinion one possibility is that this crash occurs because of the language selected for use Gnucash. I use Portuguese Brazil (pt_BR). I suspected of the program I have installed called "TuneUp Utilities" it is constantly downgrades processes to "Increase the speed of reaction of the machine." But as I have so same crash on my Win7 without this program my suspicions became weak. I think I can give some help. I'm not a complete layman, I program a little in VB and a little less in javasript but practice sporadically. I was apprehensive with your answer if you do not know what happens I find it hard to be a solution. You said do not know this crach happens to others It may be because not happens or why not complain and exchange your financial application. We must admit that this seems like a much easier solution. At least you gave me a direction I will work emphasizing the possibility that it just occurred to me. This led me to think about testing GnuCash on a WinXP system new and clean. I have an image backup of my system immediately after installed and have another HDD with this system ready for emergences or test use. Well, I have much work ahead. Please do not stop to get involved in solving this problem, you're my only hope. Remember, the hardest are the best :) Once I have I will post here the results of my tests. Best regards.
Created attachment 242297 [details] GnuCash Tracefiles Win7.rar Here is attached all tracefile I found here on Win7. Are twenty-seven files compressed in .rar format.
Hello Lords (and Ladies) GnuCash developers, I have good news. I did some testing on WinXP, I noticed something interesting that might be the cause (not the source) of the crash and managed to capture screens before during and after the Crash. See attachments. In my opinion somehow GnuCash devoured all memory and caused the crash. At least I believe that monitoring memory usage I can predict the Crash and protect me before. It is possible that this bug is related to the Bugs 670491 and 690786 which I found so far. Best Regards. Tes
Created attachment 242477 [details] Screenshot WinXP Msgs Crash & Attempted to Capture Screen After a Crash was displayed a crash message without title bar. The first attempts to capture the screen failed and produced the second message of memory with Caption "Error". Dragging this msg on the other made the title of the msg crash be displayed. I waited and some memory was released, it was when I got this screen capture. Note the system resources monitor charts displayed in the upper right. Your captions and absolute values can be seen in the next screenshot.
Created attachment 242479 [details] Screenshot WinXP - Decline in the use Memory After Close Gnucash Notice in the upper right second chart from left to right the sudden drop in memory usage after closing GnuCash and messages of crash and memory failure shown in previous attachment. Charts captions and absolute values can be seen in the next screenshot.
Created attachment 242482 [details] Typical memory usage with GnuCash closed Notice in the upper right corner the charts and on the bottom left the absolute values of typical memory usage with GnuCash closed.
Created attachment 242484 [details] Typical memory usage with GnuCash just opened Notice the charts in the upper right corner and the absolute values on the bottom left of the typical memory usage with GnuCash just opened.
Created attachment 243019 [details] WinXP SysInfos - 2013-05-02.txt Follow the System Information. Regards.
Here are the latest results of my tests: I noticed that I can let GnuCash open for hours while working on other things that no crash occurs. I tested the v2.4.12 with new theme and crash continued occurring while I worked with Gnucash. I removed the v2.4.12 and installed the v2.4.11 which inherited the previously selected theme and the result was: Crash, Crash and more Crash. (Errors occurred during uninstall of v2.4.12 during installing the v2.4.11 and during resettlement of v2.4.11 for test whether the error would be corrected as recommended in the msg error. Screenshots will be attached.) Reported below is what I was doing at the time the crashes occurred at 2013/05/04: * I imported an OFX file from Android GnuCash and when I was editing the imported transactions the crash occurred. I disabled auto-save that was set to 3 minutes and follow working doing manual saves. * When I was editing exchange rates (Right Click on Transaction> Edit the Exchange Rate> Enter value for exchange rate> Click button Exchange Rate> Ok> Enter) and manual save of approximately 10 to 10 entries. * During a transfer when i adjusted the date. * After working for about 15min doing transfers when I clicked the transfer button. * Again after working for about 15min doing transfers when I clicked the transfer button. * I removed the division of the transaction and when I was editing the account of the transaction. * Editing exchange rates of various transactions. After all these crashes I left Gnucash without activity for hours which was without any problems. Observed in v2.4.11 that crashes occurred when the memory was not exhausted and there was still memory available. Screenshots take just after crash will be attached. Also attached will be the tracefiles the same period of time that these crashes occurred. Since some variables were eliminated and the behavior of GnuCash has not changed, I intend to go back to v2.4.12. I await suggestions and guidelines. Regards. Tes.
Created attachment 243418 [details] Screenshot WinXP - Error in the uninstallation of v2.4.12.JPG Screenshot WinXP - Error in the uninstallation of v2.4.12
Created attachment 243419 [details] Screenshot WinXP - Error installing the v2.4.11.JPG Screenshot WinXP - Error installing the v2.4.11
Created attachment 243420 [details] Screenshot WinXP - Error in reinstalling of v2.4.11 when the installer removing v2.4.11.JPG Screenshot WinXP - Error in reinstalling of v2.4.11 when the installer removing v2.4.11 for test whether the error would be corrected as recommended in the msg error.
Created attachment 243421 [details] Screenshot WinXP - Error in reinstalling of v2.4.11 when the installer reinstalling v2.4.11.JPG Screenshot WinXP - Error in reinstalling of v2.4.11 when the installer reinstalling v2.4.11 for test whether the error would be corrected as recommended in the msg error.
Created attachment 243423 [details] Screenshot WinXP - v2.4.11 - Crash and attempted to capture screen.JPG Screenshot WinXP - v2.4.11 - Crash and attempted to capture screen. Notice in the upper right second chart from left to right the memory usage some time after crash when it was possible to capture the screen.
Created attachment 243432 [details] Screenshot WinXP - v2.4.11 - Memory usage After Crash and Close Gnucash.JPG Screenshot WinXP - v2.4.11 - Memory usage After Crash and Close Gnucash: This screen was captured after waiting the release of any memory to be possible to make a screenshot and after closing GnuCash crashed. Notice in the upper right second chart from left to right the sudden drop in memory usage after closing GnuCash crashed and memory failure message shown in previous attachment. Notice in the bottom left the absolute values of memory usage with GnuCash recently closed after crash and after it was possible to capture the screen.
Created attachment 243436 [details] Screenshot WinXP - v2.4.11 - Memory Usage Before & After Crash.JPG This screen was captured after closing GnuCash crashed. Notice in the upper right second chart from left to right the behavior of memory usage. Notice in the bottom left the absolute values of memory usage with GnuCash recently closed after crash. Notice that in this crash apparently the memory was not exhausted.
Created attachment 243437 [details] GnuCash 2.4.11 on WinXP Tracefiles 2013-05-04 & 05.rar Here are attached the tracefile for the last crashes of the v2.4.11 on WinXP at 2013/05/04.
Tes, thank you for all the additional information. A couple of things: * If you experienced ofx import issues with GnuCash 2.4.12, that's normal. There unfortunately was a serious bug in that area in the Windows release. This has been fixed in GnuCash version 2.4.13. * Your screenshots illustrate that something goes wrong already during the installation of GnuCash. If the installation is not running properly, you can't expect the program to function properly afterwards. So let's focus on the installation error message. * The message looks to me like written in Portuguese. With some googling an guessing, I think it translates to something like this: Application has failed to start because framedyn.dll was not found I have googled this and got to this page: http://support.microsoft.com/kb/319114 I looks like you have a problem with your Windows Installation. The webpage contains ways to fix this. I suggest you try this first, then reinstall GnuCash and test if your memory problem is gone. Can you add your findings to this report afterwards ?
Hello, Dear Geert Janssens, Thank you for your manifestation I was already feeling lonely here. "* If you experienced ofx import issues with GnuCash 2.4.12, that's normal. There unfortunately was a serious bug in that area in the Windows release. This has been fixed in GnuCash version 2.4.13." There were crashes without make imports and after importations. I don't remember crash during importations. Until now I only imported OFX files from GnuCash Android and the only problems I experienced during import was: * GnuCash does not recognize Portuguese specific character like "ç", "é", "ê". I checked within OFX file and characters are OK there. * The names of the accounts to linking displayed in the window of the importer is difficult to recognize because it is displayed in part of original characters and the remainder in other characters. I believe this is blamed of the OFX file generated by GnuCash Android. "* Your screenshots illustrate that something goes wrong already during the installation of GnuCash. If the installation is not running properly, you can't expect the program to function properly afterwards. So let's focus on the installation error message." Yes of course. But I inform you that this problem only happened in this last installation (v2.4.11) and not in previous installation (v2.4.12) where there was also crashes. On 2013/05/08 I searched on my PC framedyn.dll that netsh.exe (Network Diagnostic) complained that was missing. I found it in C:\WINDOWS\system32\wbem and I intuitively copied to C:\WINDOWS\system32. After that netsh.exe no longer complains and works well. I believe so I have solved the problem. It now remains repeat the GnuCash installation without errors to eliminate this variable. "* The message looks to me like written in Portuguese. With some googling an guessing, I think it translates to something like this: Application has failed to start because framedyn.dll was not found" Yes, that's it. "I have googled this and got to this page: http://support.microsoft.com/kb/319114 I looks like you have a problem with your Windows Installation. The webpage contains ways to fix this. I suggest you try this first, then reinstall GnuCash and test if your memory problem is gone." Again I fixed the problem by the way recommended by Microsoft. Somehow my PATH system variable was gone. I reintroduce it. Thank you, this information was of great help. I googled a lot but I had not found this. I'll remove and reinstall v2.4.11 and test it again. "Can you add your findings to this report afterwards ?" Yes of course. As soon as I have them I'll put them here. Best Regards Tes.
I have set up the "Process Monitor" (Free Download - 1 077 KB - http://technet.microsoft.com/en-us/sysinternals/bb896645) to monitor the GnuCash and then I generated a crash. Now we have the "Process Monitor" LOG that could help us to analyze the crash. I analyzed it but I could not tell what the cause of the crash. For this It is necessary to understand the GnuCash code. This logs file will be attached.
Created attachment 244114 [details] Files for analysis by "Process Monitor" Part01 (.rar) Process Monitor Files.part01.rar (By Bugzilla limitations the file was divided into two parts.) I worked without saving and could not generate the crash, I worked saving and managed to generate crash. This compressed (.rar) package contains the "Process Monitor" configuration file (.pmc), the log files generated by the "Process Monitor" exported in three formats (.pml,.csv,.xml), file containing the "Process Monitor" Logfile Points (.txt), and GnuCash tracefiles corresponding a this generated crash for tests. ("Process Monitor" Free Download - 1 077 KB - http://technet.microsoft.com/en-us/sysinternals/bb896645)
Created attachment 244115 [details] Files for analysis by "Process Monitor" Part02 (.rar) Process Monitor Files.part02.rar (By Bugzilla limitations the file was divided into two parts.) I worked without saving and could not generate the crash, I worked saving and managed to generate crash. This compressed (.rar) package contains the "Process Monitor" configuration file (.pmc), the log files generated by the "Process Monitor" exported in three formats (.pml,.csv,.xml), file containing the "Process Monitor" Logfile Points (.txt), and GnuCash tracefiles corresponding a this generated crash for tests. ("Process Monitor" Free Download - 1 077 KB - http://technet.microsoft.com/en-us/sysinternals/bb896645)
In a quick googled I found complaints similar to this my complaint (GnuCash Runtime Error). Surely I'm not alone, I am not the only one who have this problem and this problem is old and has many different causes and solutions as can be seen in some links below: * http://gnucash.1415818.n4.nabble.com/GnuCash-2-4-10-released-td4362837i20.html (rsbrux) * http://gnucash.1415818.n4.nabble.com/Unspecified-Fatal-Error-td1426211.html (Richard Ullger) * http://lists.gnucash.org/pipermail/gnucash-user/2011-January/038161.html * http://sourceforge.net/p/gnucashportable/discussion/752617/thread/5399acaa/ The only firewall I use is Windows Firewall and my Antivirus is the avast! I intend to test with them off. I also want to remove all spaces from the path of gnucash.exe currently in (C:\Arquivos de programas\gnucash\bin\gnucash.exe) how to install it in C:\ and take tests. To isolate the cause I plan to test one at a time. Any suggestions or advice is welcome. Best Regards Tes.
Here is the latest results of my tests: 2013/05/13 - After correcting the problem of lack of the "PATH" system environment variable by the way recommended by Microsoft the installation of v2.4.11 over v2.4.11 already installed ran fine. All instalation process went right and without any problems. :) After that I started testing the v2.4.11 and the result was: CRASH again. Below is described what I was doing at the time that a few crash occurred: * After editing several exchange rates and save SOMETIMES when right clicked on a transaction and selected "Edit Exchange Rates". I noticed that my memory was not exhausted. It was 60% but I get a msg "out of memory" when I tried to do a screenshot. * Again after editing several exchange rates and save ONE TIME when right clicked on a transaction and selected "Edit Exchange Rates". Tracefiles regarding test dates will be attached. 2013/05/14 - I turned off the antivirus and Windows Firewall and I continued testing and the crashes continued to occur. Crash occurred when: * After editing several exchange rates and save TWO TIME when right clicked on a transaction the pop-up menu appeared and seconds later the crash occurred. I did tests without saving and crash continued to occur while I worked. :( Tracefiles regarding test dates will be attached. I configured the "Process Monitor" to monitor GnuCash and worked on it until crash occurred. Files for analysis by the "Process Monitor" will also be attached. My creativity to invent test and my alternatives are exhausting. At the moment I only have two more testing to do. Install GnuCash on C:\ to remove the spaces in the gnucash.exe path and install it on another HDD with a new and clean WinXP system. My only workaround so far is working for some time (Hoping... in expectation not to be surprised by a crash and lose all the work and forget what I was doing and had to do), save, close, open, and repeat this process to gain some more time to work. Again I await suggestions and guidelines. Best Regards Tes.
Created attachment 244263 [details] Tracefiles WinXP - v2.4.11 - 2013-05-13 & 14 (.rar) Tracefiles regarding test date 2013/05/13 & 14.
Created attachment 244264 [details] Tracefiles WinXP - v2.4.11 - 2013-05-14 (.rar) Tracefiles regarding test date 2013/05/14.
Created attachment 244265 [details] Process Monitor Files.2013-05-14.part01 (.rar) Files for analysis by "Process Monitor" at 2013-05-14 Part01 (.rar) (By Bugzilla limitations the file was divided into two parts.) This compressed (.rar) package contains the "Process Monitor" configuration file (.pmc), the log files generated by the "Process Monitor" exported in three formats (.pml,.csv,.xml), file containing the "Process Monitor" Logfile Points (.txt), and GnuCash tracefiles corresponding a this generated crash for tests. ("Process Monitor" Free Download - 1 077 KB - http://technet.microsoft.com/en-us/sysinternals/bb896645)
Created attachment 244266 [details] Process Monitor Files.2013-05-14.part02 (.rar) Files for analysis by "Process Monitor" at 2013-05-14 Part02 (.rar) (By Bugzilla limitations the file was divided into two parts.) This compressed (.rar) package contains the "Process Monitor" configuration file (.pmc), the log files generated by the "Process Monitor" exported in three formats (.pml,.csv,.xml), file containing the "Process Monitor" Logfile Points (.txt), and GnuCash tracefiles corresponding a this generated crash for tests. ("Process Monitor" Free Download - 1 077 KB - http://technet.microsoft.com/en-us/sysinternals/bb896645)
Tes, lots of information here, thank you. It's good that the installation error has been eliminated, but unfortunate that it didn't solve your crash :( Regarding the log files you have attached, they almost all still show the g_date_compare error I have already pointed out before. I'm not sure it is relevant though. You may want to try with a different language setting on your system (if you have that option) and see if this error message still remains. My guess is this error is due to some date format that is not recognized by the localization libraries we use (gtk/gnome). I have loaded your process monitor log files in sysinternals' process monitor. I have never used that tool, so I'm not sure what I should look at. As a first impression it shows your are using the transfer dialog a lot (which matches your remark about doing a lot of exchange rate modifications). But with my limited understanding of this program I can't see the cause of the crash in here. Regarding your tests you have yet to run: don't bother with the test of installing in a patch without any spaces. That's not related at all to this problem. GnuCash wouldn't have started properly if that was a problem. You may want to try to install on a completely clean system, only Windows XP and GnuCash, with optionally an anti-virus program. No other tools or stuff. Then see if the crash is still easily repeatable. So far it looks like a memory leak somewhere, but I have no experience in debugging such leaks. A last test I just came up with: was there any version of GnuCash that didn't have this problem ? Or was 2.4.11/2.4.12 the first version of Gnucash you worked with ? Lastly, as a reply to your comment 31. "Runtime error" is a very generic error description, used by Microsoft to signal that something irrecoverable happened during the runtime of the program. This can be anything. The links you add in that comment are all unrelated to this issue. The first one deals with a bad library in GnuCash 2.4.10 that got replaced in GnuCash 2.4.10-1. Several others refer to an issue with some firewalls, but is basically not a GnuCash error and can be worked around fairly easily. Your problem seems to be some memory leak. You'd expect this to affect many users though, but curiously enough you are the first one to hit it with the two versions you have tested. There are no other reports. That doesn't mean you issue isn't valid. Maybe you use GnuCash slightly differently from other users that triggers this memory issue more quickly. Perhaps it's not a memory leak but rather something wrong on your PC. We still have to determine this by running GnuCash on a clean Windows installation. The fact that your path was no longer set is already a clue that something is not right. You have fixed that, but there may be other issues. On the other hand, I'd be fairly uncommon to have the same issue on two pc's, with a different version of the os.
Hello, Dear Geert Janssens, Again thank you for your attention. "I have loaded your process monitor log files in sysinternals' process monitor. I have never used that tool, so I'm not sure what I should look at. As a first impression it shows your are using the transfer dialog a lot (which matches your remark about doing a lot of exchange rate modifications). But with my limited understanding of this program I can't see the cause of the crash in here." I have even more limited knowledge that yours but in my guess is that "Events" that have "Results" like "BUFFER OVERFLOW", "NAME NOT FOUND", "PATH NOT FOUND", "RANGE NOT LOCKED", "NO SUCH FILE", "FILES NO MORE", "NO MORE ENTRIES" are suspects and maybe deserves to be investigated in the GnuCash code its consequences. Also the last file (libglib-2.0-0.dll) accessed by GnuCash when occurs the crash appears to be important for investigate the cause of the crash. "Regarding your tests you have yet to run: don't bother with the test of installing in a patch without any spaces. That's not related at all to this problem. GnuCash wouldn't have started properly if that was a problem." Thanks for the suggestion. You saved me some unnecessary work. I think that it would only be relevant to the case of GnuCash Portable used with "Portableapps" (http://portableapps.com/) "A last test I just came up with: was there any version of GnuCash that didn't have this problem ? Or was 2.4.11/2.4.12 the first version of Gnucash you worked with ?" "Your problem seems to be some memory leak. You'd expect this to affect many users though, but curiously enough you are the first one to hit it with the two versions you have tested. There are no other reports." A long time I was looking for a financial SW that works with muiti-currency and small businesses and in 2012 I found by chance GnuCash Portable v2.4.11 among "Portableapps" applications (http://portableapps.com/). I tested and liked it, but in the first tests I noticed the crashes. I did not bother because I thought it was problem of my system and I planned to format my PC soon or an update of Gnucash could correct the problem. After that I've formatted my PC and now came a new version v2.4.12 and when I take the use of Gnucash realized that the crashes still occur. It was when I decides fetch for your help instead of abandoning its use. If I had chosen to abandon the GnuCash use you would not have a single case of a complaint of this issue. This issue works as a very powerful method for GnuCash users selection. Also, for everything there is a first time. It's not what I think but many people think it will not be well assisted by complaining of a free open source SW. "Lastly, as a reply to your comment 31. "Runtime error" is a very generic error description, used by Microsoft to signal that something irrecoverable happened during the runtime of the program. This can be anything. The links you add in that comment are all unrelated to this issue. The first one deals with a bad library in GnuCash 2.4.10 that got replaced in GnuCash 2.4.10-1. Several others refer to an issue with some firewalls, but is basically not a GnuCash error and can be worked around fairly easily." Yes, I understand. As I have said before here, I write a bit of code in VB and Java and I have some experience with "RunTime Error". I meant to just say that "RunTime Error" happen to everyone and not just with me as well as said too it has many different causes and solutions. "You may want to try with a different language setting on your system (if you have that option) and see if this error message still remains. My guess is this error is due to some date format that is not recognized by the localization libraries we use (gtk/gnome)." I also had this guess as I reported in my Comment 9. Now reinforced by your guess I'll do this test. I tell of GnuCash in English on OS in Portuguese or Spanish. If you are talking about OS in English this would be a laborious test because I do not have an OS ready in English. "That doesn't mean you issue isn't valid. Maybe you use GnuCash slightly differently from other users that triggers this memory issue more quickly. Perhaps it's not a memory leak but rather something wrong on your PC. We still have to determine this by running GnuCash on a clean Windows installation. The fact that your path was no longer set is already a clue that something is not right. You have fixed that, but there may be other issues. On the other hand, I'd be fairly uncommon to have the same issue on two pc's, with a different version of the os." Yes, I'll test on a clean WinXP system. Also curious is that my other Win7 system where also crashes occurred is in Spanish but with an installation of GnuCash in Portuguese. Barbarity! :) This reinforces our guesses about a possible problem with the installation of GnuCash in Portuguese and I do not believe that in Brazil 10% of people speak English enough to come here to make a claim like this mine if us also consider my technical knowledge this number drops to less than 1% of the Brazilian population which would explain the lack of such claim. After, if necessary, I plan also testing install a English GnuCash on a Portuguese clean WinXP. I have HDDs, backups and VMs ready for, if required, in seconds climb up even a war system. Just kidding! :) Thank you! Best Regards Tes.
Hello, Dear Geert Janssens, Here are the latest results of my tests: As I said at the beginning of this Bug report, something very curious and suspicious occurs after I click on the Gnucash installer in my current systems WinXP and Win7: After clicking the Gnucash installer a "Select Setup Language" box, is displayed, if I click or manipulate the Drop-Down menu language selection or move this box, it disappears subtly and after that, every time I click the installer (Tested for 2.4.11, 2.4.12 or 2.4.13) the box appears and briefly then immediately closes. Occurred so I can only make the "Select Setup Language" box remains displayed by running the installer from DOS. With the box displayed and without touching anything more, I click on the "OK" button and the installation continues without further problems. Even run from DOS, if I click on something other than "OK" button the box also disappears and the problem returns, it does not stays longer displayed. On 2013/05/16 I installed Gnucash 2.4.13(pt_BR) on a WinXP(pt_BR) Basic(With the 1st MS updates offered, Adobe Flash Player 11, avast! 7, Chrome, Java 7, MS Office Pro Plus 2010 IE8, MS W. Media Player 11, WinRar 4) system by the following procedure: I clicked on the installer then clicked on the "Run" button in the "Open File - Security Warning" box then clicked ONLY on the "OK" button in the "Select Setup Language" and Gnucash was installed without problems. After the successful installation of 2.4.13, I performed tests in the "Select Setup Language" box from versions 2.4.11, 2.4.12 and 2.4.13 by the following procedure: Clicked on Installers Gnucash then clicked on "Run" button in the "Open File - Security Warning" box (only to 2:11:13) then moved the box several times and clicked thoroughly on Drop-Down menu of the 2.4.11, 2.4.12 and 2.4.13 boxes and all went well and smoothly which was a great indication that the following tests could have good results as well. :) I started the Gnucash 2.4.13(pt_BR) test on WinXP(pt_BR) basics to try to reproduce the previously crashes occurred in my current WinXP(pt_BR) and Win7(es_ES) systems. The test was run using the same sequence of work to edit exchange rates that previously produced crash which consists of: Right click on a transaction, click "Edit Exchange Rate" on pop-up menu, change the value of "Exchange Rate", click on "Exchange Rate:" button, click the "OK" button and press the "ENTER" key. 64 transactions were edited by 6 times by saving 15 or 30 transactions. The result of the test was: NONE CRASHES OCCURRED. This result looks great but still can not tell us the crashes cause. Without knowing the crash origin we only work on hunches. How could we know if the Gnucash instability is my fault or my systems fault or Gnucash code fault? How will we know if the Gnucash instability was not produced by a installer issue, by a Gnucash Bug, by an incompatibility with another program, with a Windows update or Windows component or any other characteristic of normal use little used? I add that in both my WinXP and Win7 systems where occur the crashes I have no problems with this gravity with no other program. Only Gnucash presents this sensitivity, this instability and this fatal error. In a damaged system is not only a program that suffers, is more than one or all, and it is unwise condemn an entire system due to faulty in a single program. It would be good for all that the cause of the crashes it were something rare, unusual and isolated as some damage on my current systems WinXP, Win7 produced by users or any other reason. In this case the solution would be very simple, would suffice I to abandon the old systems and climb a new backup like this that I used for the test that produced no crashes and then apologize with you developers. These tests and reports already cost me a lot more work than one a new system preparation. Working only on hunches stays the risk again be surprised by new instabilities and crashes again after formatting and preparing my desktop for a second time. Only have a few months since I formatted. My current WinXP work environment in which the crashes occur was prepared using as base that WinXP Basic system used in successful test of Gnucash. On 2013/05/19 I removed 2.4.11 and installed 2.4.13 on my current WinXP to test the same file and version tested on WinXP Basic. After working a bit and save without problems I went on "Content" (F1) read some threads, after some time I closed and open again when I got the lack of memory msg (See attached Screenshot), I clicked on it and Gnucash closed. Now for the first time I received a differently msg crash, maybe it can be helpful to find the cause. In short, after all my tests, we only know that the cause could be anything. I sent a post to the mailing list [gnucash-br] that has fewer than 180 registered members and so far only received a response. I'm not sure what I could do more. It is likely that the solution does not depend on me. If the developers were able to reproduce these crashes to better study the cause It would be more productive and would generate better outcomes and solutions. I could provide all the necessary information that has not been provided even a image of these suspects systems. Thank you. Best regards Tes.
Created attachment 244860 [details] Screenshot WinXP - Lack memory after clicking menu Content F1 (.JPG) The msg text is written in pt_BR and translated into en_US would be something like: "Not enough memory for this task. Close one or more programs to increase available memory and try again."
Created attachment 244861 [details] Screenshot WinXP Basic - 2013-05-16 - Select Setup Language box (.JPG) 2.4.13 "Select Setup Language" box on WinXP Basic run fine.
Two information I forgot to mension: * The old crash message also occurs with 2.4.13 on current WinXP. * I use the Win7 by RDP (Remote Desktop). Thank you. Best regards Tes.
I tested the 2.4.10 on my current WinXP. Result: CRASH. Thank you. Best regards Tes.
I'm lost in the giantic amounts of text here. Unfortunately this makes this bugreport rather useless and it makes it unlikely to have this issue fixed. From what I understand, the bug is about a crash in the "Transfer" dialog, but occurs only after heavy usage of that dialog. The crash appears on windows and in 2.4.10 and 2.4.13. As your last comment#43 says "Result:CRASH", do you mean you did a specific series of steps that inevitably resulted in a crash? If that is the case, please list the steps here so that we can reproduce this crash ourselves. On the other hand, if you mean the crash occurred after entering dozens of transactions at some seemingly random point in time, it will mean we will not be able to reproduce this crash at our development environment, which makes it much harder to fix this. In any case: Please open a new bugreport with *only* the part that is relevant to the crashing bug. We'll close this report because any reader is lost within tons of information here. Don't explain each and every idea that you have - just add the information that is relevant to the crash. Thanks!
Dear Christian Stimming, The bug is about a crash in the "Transfer" dialog but not only in this case. There are several other occasions. Apparently, any gnucash nanipulação that I do the Bug occurs after a certain time. I tested (used) versions 2.4.10, 2.4.11, 2.4.12 and 2.4.13 (currently in use) on Windows XP and Seven and all occurred Bugs. Eg. On 2013/06/22 I just opened the Gnucash and went to do an import from a Android Gnucash exported OFX file while I corrected the settings of importing of some three pages of records the crashes occurred before I conclude all correction and me prevented him from doing the import (2.4.13). I also noticed that in the records account window if I keep moving the sidebar scrolls up and down the memory occupied will increasing at a steep ramp up to totally exhaust the memory. Truth, it has tons of information here, but while the status was "Status: NEEDINFO" and you did not respond I thought you were waiting for more information. How could anyone think differently about this? I'll open a new bug and try satisfszer your requirements. Thank you Best regards Tes.
Reassign version to 2.4.x so that individual 2.4 versions can be retired.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=698094. Please update any external references or bookmarks.