Whenever Panorama X launches, it automatically checks to see if the previous session ended with a crash, and if so, it automatically sends the crash report to provue’s server. It also symbolicates the report, so it actually contains more useful information than the crash message you see on your end.
So I can see that in the past two days you have had a bunch of identical crashes on both your MacBook and your Mac mini. Even with symbolication, it’s unfortunately very difficult to glean useful information from crash reports. I can tell you that though this may be triggered by a procedure, the crash is actually occurring in a Text Display object. This object is attempting to display a field and it would appear that the data in the field is corrupted somehow. So it may be that the problem is in your code, or it may be a problem with the actual data. Is this database being shared between computers somehow? Maybe Dropbox or file sharing? Possibly exporting and then re-importing the text might help? Though I’ve never heard of a problem like that with Panorama X, but I suppose there is always a first time (and the problem could have originated with a hardware glitch, then spread across machines via sharing).
I don’t see any record of a crash on your Mac Pro, but if you didn’t launch Panorama again on that machine, the report won’t have been submitted yet.