Created attachment 276 [details]
I am using the import comma separated values function. A screenshot of the error is attached. There is a significant spike in CPU usage, but none in memory usage. The first few lines of the file are copied below. The file has 1048577 lines. Please let me know if you would like me to send you the csv file. I could only attach one file.
I do understand that I am probably using the import wrong.
"Time","ALE","A","D","RAM /CE"," ROM /CE","/G (PERIPHERAL DATA BUFFER)","/OE","/WR","/G (INTERRUPT BUFFER)","/IR","PD","INTR","/INTA","IO/M","S1","S0"
You run the software on Windows. Does the last line of the CSV file miss
the line termination perhaps, which seems to be rather popular there? In
that case the report is a duplicate of bug 635, and a fix will be available
soon. Does the file have the (unnecessary) BOM perhaps? In that case the
report would be a duplicate of bug 756 (soon to get fixed, too). Did you
tick the "Header" checkbox in the CSV input configuration dialog?
It's probably best if you could provide a short file that reproduces the
issue. Thank you!
The sample provided has a few more complications, e.g. analog/float value as first column, various logic columns, two hex-byte columns ("FF", "FB"). Not sure if all of that is supported, yet.
Ian, does this still happen with a current PV nightly build?
Closing due to user inactivity. It's been a year without an answer.
really close, feel free to re-open when the issue persists, but do provide
feedback and details when asked
Did a quick re-test with recent software, works as expected. Command line
options were: -I csv:column_formats=-,l,x16,x8,6l,x4,x8,5l (guessed).