I have had TFB (17.1 x64 reading Solaris 19.25.0.0 files) freeze around 95% into processing files over the past couple of days. It blocks all Toad and I have to kill the entire app. Is there a way to less painfully cancel TFB when it is chewing input files and has some hanging event? If not can we get one?
Just curious... how large is/are the trace file/s?
Browsing a copy of the trace file?
60-80mb. I processed several before and after. I just had 2-3 last night that made it lock up. It's really random. I just ran the same process that made an 89mb file and it processed it fine in 12 sec.
Hey Chuck,
Is there a way to less painfully cancel TFB when it is chewing input files and has some hanging event? If not can we get one?
No, there isn't, and I can add one.....but....TFB should never hang while processing trace files. So I'd really like to fix the problem.
60-80 MB should be nothing for TFB. Can you zip it up and email it to me? john.dorlon@quest.com
FYI: If you have any "CursorDiagnosticNodes" sections in your trace files, this was a bug fixed in version 2024.2, but from what I saw, that caused errors, not hangs.
-John
I can't provide the file in its entirety from that particular environment. I have a near sanitized small excerpt from it. It fails until I sanitize the node name to anything else of the same length. It's just 3 entries in the Node name, Unix process, and MODULE NAME. If I change them it processes fine. It is Friday the 13th. I should know better!
Hm. I would not expect those values to have any impact at all.
There's no strange characters in there? What if you look with a hex editor? Can you see any characters that shouldn't be there that way?
When we start loading the file, the first thing we do is skip down to a line that looks like the following, not including quotes.
'====================='
So I am guessing there is some kind of unprintable character in your node name/unix process/module name which is causing havoc.
Hey Chuck,
Not sure if this is related to what you were seeing or not, but the "Processing Statements" step will be much faster next beta. Like, so much faster, you'll wonder if that part even ran.
-John