Crash (EXC_BAD_ACCESS) for no apparent reason #282

Closed
hsoft opened this Issue Jun 22, 2013 · 16 comments

Projects

None yet

1 participant

@hsoft
Owner
hsoft commented Jun 22, 2013

MoneyGuru (on Mac OS 10.7.1, 64-bits) regularly crashes for no apparent reason. I could no link this crash to a specific task or view. However, it happens regularly (more than once per hour of use), at least since version 2.3.9 and Mac OS 10.6.

I attach a typical crash report to this ticket. All crash reports look the same, except for the "exception codes" that vary in their location:

@@@
KERN_INVALID_ADDRESS at 0x0000000000000018
0x000000000000000d, 0x0000000000000000
KERN_INVALID_ADDRESS at 0x00007fff95332eaf
KERN_INVALID_ADDRESS at 0x0000000000000011
KERN_INVALID_ADDRESS at 0x00000000000002ff
KERN_INVALID_ADDRESS at 0x0000000000000004
@@@

@hsoft hsoft closed this Jun 22, 2013
@hsoft
Owner
hsoft commented Jun 22, 2013

My first guess would have been some kind of "haxies" causing a crash, like it often happens, but when I look at the crash report I only see Antidote (an anti virus right?). Have you been using moneyGuru for a long time? Do these crashes started only recently? Is the install of Antidote recent? Is it possible to disable it for a while to see if you get these crash?

If it's not the anti virus, would you mind reverting to v2.3.8 for a while to see if it crashes as well?

@hsoft
Owner
hsoft commented Jun 22, 2013

Hello Virgil. Thanks for your quick answer. I really appreciate the work you put into this great app.

I've been playing with MoneyGuru for a while (before version 2), but have started using it seriously for all my accounting only a couple of months ago. I've noticed stability issues from the start. I've been using Antidote long before MoneyGuru.

Antidote is a french grammar corrector. It adds an item to contextual menus on text fields, which probably explains why MoneyGuru loads that code. The next time I use MoneyGuru, I'll try to move the two Antidote libraries listed in the log so that they don't get loaded.

I also use the free Sophos Anti-Virus. I didn't see any of its code listed in the log. Do you think it could still be a problem?

Otherwise, I'll revert to 2.3.8 as you requested.

I'll keep you updated.

@hsoft
Owner
hsoft commented Jun 22, 2013

OK, it isn't Antidote. I just had a crash with Antidote uninstalled (the libraries are not listed in the crash report).

I'll try 2.3.8 for a while see how it goes.

@hsoft
Owner
hsoft commented Jun 22, 2013

One other possibility could be a hardware problem. Does it happen with other apps?

Another interesting thing to try would be (because you mention "more than once per hour of use") to simply let moneyGuru run without touching it and see if it crashes too. In other words, see if the crash is related to usage.

I know it's a lot of poking around, but with this kind of bug, there's not much else to do.

@hsoft
Owner
hsoft commented Jun 22, 2013

So, the latest news are:

  • 2.3.8 crashes also. Should I continue trying earlier versions?
  • There are no crashes when the application remains idle. Something (but what?) must happen for it to crash.
  • I do not have any other application randomly crashing like MoneyGuru.

I also thought about something other. The MoneyGuru document is located in an encrypted disk image synchronised with Drop Box. Maybe there is something fishy happening with that. I'll try moving the file to a normal location and sees what happens.

@hsoft
Owner
hsoft commented Jun 22, 2013

OK, I've found a way to reproduce this issue consistently:

Given a document with at least one account group containing at least one account.

  1. Exclude (gray-out) at least one account in an account group. Alternatively, exclude the whole account group.
  2. Close the account group.
  3. Open it.
  4. Close it again.
  5. CRASH!

It happens for any account, both in Net Worth and Profit & Loss.

I was able to reproduce this bug on a fresh document containing only one group and one account.

Can someone else reproduce it?

@hsoft
Owner
hsoft commented Jun 22, 2013

Yup, I can reproduce it. That's a really good catch, thanks!

@hsoft
Owner
hsoft commented Jun 22, 2013

Ok, the exclusion part isn't actually needed:

Given a document with at least one account group containing at least one account.

  1. Close an account group.
  2. Open it.
  3. Close it again.
  4. CRASH!

The crash can also be reproduced by closing and opening different accounts, but usually requires more clicks. In rare cases involving different accounts, the crash happens when opening an account, rather than when closing it.

@hsoft
Owner
hsoft commented Jun 22, 2013

Cool. Thanks Virgil.

@hsoft
Owner
hsoft commented Jun 22, 2013

That's strange, I wonder when that crash was introduced.

@hsoft
Owner
hsoft commented Jun 22, 2013

Another interesting observation: The crash reproduced above doesn't happen in Snow Leopard. So whatever caused random crash earlier wasn't it.

@hsoft
Owner
hsoft commented Jun 22, 2013

Oh, now it gets interesting. The folder tree in dupeGuru also crashes in the same way when a subnode is expanded/collapsed in the way described above. The plot thickens...

@hsoft
Owner
hsoft commented Jun 22, 2013

I tried finding a MoneyGuru crash report from Snow Leopard to compare it with those from Lion. Unfortunately, I couldn't find any. Maybe they where erased during the update process. Sorry.

@hsoft
Owner
hsoft commented Jun 22, 2013

(from [a0ac099706b4]) [#282 state:fixed] Fixed crash curring account groups expand/collapse under OS X Lion.
https://bitbucket.org/hsoft/moneyguru/changeset/a0ac099706b4/

@hsoft
Owner
hsoft commented Jun 22, 2013

@Gilles: The group expand/collapse issue took over this ticket even though it seems that there might be other causes for the random crashes you were getting, but after the release of the next version, which will contain this latest fix, please create another ticket if you experience another crash.

@hsoft
Owner
hsoft commented Jun 22, 2013

Just to let you know: I think that your fix resolved all causes that bothered me. I did not encounter any crash since the release of 2.3.11. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment