[Kst] Wht's left for 2.0.8 ?

Peter Kümmel syntheticpp at gmx.net
Thu Dec 19 06:06:33 UTC 2013

Hi Ben,

many thanks for this detailed feedback!

I've enabled some debug output in the ascii data reader.
Could you try to reproduce the crash when loading the live data
and post the debug output?

It now logs when reading a column starts.
Maybe this helps us to figure out what's going on.


On 16.12.2013 04:22, Ben Lewis wrote:
> There's also the "Generate vector bug" which I've added to the list below.
> On 16/12/2013 11:59 AM, Ben Lewis wrote:
>> Hi Guys,
>> I've done a small amount of testing on the latest build. It's getting close but there
>> are still some outstanding issues:
>>   * The bottom LH status bar over writes the (X,Y) coordinates with "Reading Field..." when
>>     updating live data. I think status updates from reading data should only be displayed on the
>>     initial read.
>>   * "FFT Length" is editable when "Interleaved Average" is deselected.
>>     https://bugs.kde.org/show_bug.cgi?id=328371
>>   * Time axis does not update after changing sample frequency.
>>     https://bugs.kde.org/show_bug.cgi?id=328481 It looks like the behaviour of this bug has
>>     changed but it is still not right yet. I can provide more details if required.
>>   * Kst crashes intermittently when loading live data. I can't reproduce this reliably yet but it
>>     seems that the larger the file the more likely it is to crash. I will provide more
>> details
>>     when I can find the steps to reproduce this.
>       * Generate vector bug. http://kde.6490.n7.nabble.com/Generate-vector-bug-td1552453.html
>> None critical bugs:
>>   * The length of time required to read/pass ASCII data changes dramatically from one
>> column to
>>     the next. I'm not sure if this is a bug but on the surface it looks like load times
>> could be
>>     significantly reduced if this problem was fixed.
>>   * Temporary memory is not freed after reading data from an ASCII file. As it stands at
>> the
>>     moment approximately twice as much ram is required than is really necessary.
>> I'll do some more testing and get back to you if I find anything else.
>> Regards, Ben
>> On 16/12/2013 12:36 AM, Peter Kümmel wrote:
>>> On 15.12.2013 14:21, Nicolas Brisset wrote:
>>>>> Should be fixed now. I will also disable progress information when
>>>>> the file changes.
>>>> Just tested a bit: sometimes I see "column read", sometimes "Reading field"...
>>>> Sometimes a progress bar flickering, sometimes not.
>>>> And when loading from a saved .kst file the progress still ends at 50%.
>>> Fixed with last commit.
>>>> I haven't tested all possible cases (threads yes/no, live streaming data, data wizard,
>>>> change data file, reload existing .kst, etc...) but I have the feeling it's not really
>>>> consistent.
>>>> I'd still favor the simpler solution I had implemented: progress bar when parsing the
>>>> rows and enough MB to parse, otherwise just a simple text label "Reading field:
>>>> [name]", and that's it.
>>> I don't wanna undo all the changes, and it is much better now.
>>>> Nicolas

More information about the Kst mailing list