Intermittent but regular Address Violoation Errors

RootsMagic
,
1

RM 10.0.3.0 64 bit, Windows 10 Professional 64 bit

I have been working on my long term project to process my people who are color coded yellow. This is my color code for the people in my database who are unconnected to me. Right now, I have a list of yellow people of particular interest by RIN number. This is not all the yellow people. The current list of people of interest is 39 yellow people out of a total of about 3000 yellow people.

Here is my process. I am working in People List View and in Descendant View set to 7 generations. It’s very unusual for me to set Descendant View to 7 generations, but the people I am working with are in clusters of a half a dozen to two or three dozen people, so there is no harm in setting Descendant View to 7 generations.

  • I put the RIN for the next person of interest into the search box in People List View.
  • I click the person to give them the focus. This doesn’t happen automatically even though they are the only person in People List View.
  • I switch to Descendant View
  • I process that person and the little family cluster they are in. When I get done, that person and the other people in the same cluster are no longer yellow. I may have deleted them from my database. I may have connected them to my tree, so they are no longer colored yellow. I may have colored them gray because they need further research even though I cannot connect them to my tree at the present time. So they are no longer colored yellow, no matter what.

That’s the whole process. The address violation error occurs when switching from People List View to Descendant View. It seems to happen after an hour or so, during which time I might have processed a half dozen to a dozen yellow people in this manner. It’s like RM gets tired - more likely a memory leak or something like that. Or there may be some sort of race condition between threads in RM which are running in parallel. It may take that long before the problem with a possible race condition might manifest itself. I don’t actually know what the cause is, and it is not repeatable enough to submit my database to RM.

RM would have to be willing to follow my exact process for an hour or two before the error would happen, and I think it would be almost impossible for them to follow my exact process. They would have no way of knowing what decisions I would make about deleting or connecting or recoloring the yellow people at each step. But maybe the fact that the error always happens immediately upon switching from Family List View to Descendant View could provide them with some clues.

The address violation error always happens at the very beginning of the processing for a new person. I don’t get far enough along to do any actual processing for the new person. I don’t know if the disposition of the previous yellow person has anything to do with it. It doesn’t seem to matter whether I deleted the previous yellow person or connected the previous yellow person to my tree or just colored the previous yellow person as gray.

1 Like
2

I doubt having a color (or particular color) should have anything to do with that – and they are not being refreshed.
However, switching views — that might offer some hints

3

I agree that the chances this has anything to do with color coding are zero. It surely has to do with going back and forth between Family List View and Descendant View.

I’m also suspicious that it has something to do with leaving Descendant View empty - like if I delete everybody in it. Or like when I return to Family List View that is filtered by a single RIN, it is empty because I deleted that person while in Descendant View. Except that I sometimes don’t delete anybody in the back and forth between views. Rather, I recolor and link or sometimes just recolor without linking.

4

I’ve reported the same error happening when moving between pages. Really hard to determine the last action that triggered it or if it was simply running through the lists prior. I don’t recall having deleted people prior though. I’ll have to watch for it.

5

I suspect that there is no “last action that triggered it”. I suspect it’s an accumulation of many actions over time. No matter what the last action was before the problem, the same action will not trigger it after shutting RM down and restarting RM.

6

that was my thought also – I really do not use Descendant view for example – but the error seems to present itself based on the # of recent changes I have made – the more – the more likely to occur. I suppose it could be related to what had been changed. Also, not sure if it had to do with anything related to TreeShare in background.

7

I also see this error randomly after hours of editing. I would rather it did not occur, but take it as a reminder to take a break from researching for awhile.

8

Same thing here. Seems to happen after several hours of editing and I also see it as a sign that I need to take a break.

I usually quit/restart rootsmagic when it happens as it doesn’t seem stable at that point.