That line is not in my code, but it was there (if I recall correctly) when it crashed in the debugger.
Thanks for the idea of clearing the cache…but it did not solve the problem.
Yes I understand that its probably something in the system, not my code. While I would like to help the Xojo team, I wouldn’t send off the source code. I suppose you could say it contains a lot of trade secrets.
I’m just trying it now, and its made it around the compare method (ie as passed to sort) about 30 times. There are a couple hundred files so I imagine it will take more than that until hitting the bad one.
So I ran it to crash, using System.DebugLog to show variables, and seems to be crashing on the last couple of files. My debug message says it went around 1957 times. A nice number. A good year.
The crash message says that the debug variables are not to be trusted, and from what I can see, when it crashes, everything is Nil or 0. So I am assuming these are not the real values. Bottom line though I think the debugger is of no use in this case…though the DebugLog is helpful.
Have you tried printing the file names to your log and then just loading that one file? That one file and your code leading up to the crash would be an easy way to show Xojo what’s going on.
1 Like