|Message: Re: CSV overwriting/interrupting lines in multithreaded operation||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I see that in your csv ntuple you have string columns (since we see "e-", "RadioactiveDaughter," in the line you show). One idea may be that some of the written strings contain control (then non printable characters as '\n' or worst some commas ! It is clear that if this happens the IO in itself in the file would be ok but the "CSV format in itself" would be corrupted because then you will not have the same number of items per line. For efficiency reason, for the moment, I have no check about that when writing strings...
Else yes, if some disk is full you may have problems, but if so the related program or thread would have crashed (because right now the "<<" operator is not protected) and you would have corrupted lines at the end of a badly/not-properly closed file.
Then some actions would be to check if the corrupted lines appear at end of file, and also to check (my prefered hypothesis) that your strings potentially do not contain fancy characters (including commas !).