Bug 144317 - 1.4.0: crash when changing data vector of a PSD
Summary: 1.4.0: crash when changing data vector of a PSD
Status: RESOLVED FIXED
Alias: None
Product: kst
Classification: Applications
Component: general (show other bugs)
Version: 1.x
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kst
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-16 22:50 UTC by D. V. Wiebe
Modified: 2007-05-08 21:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (5.52 KB, text/plain)
2007-04-16 22:56 UTC, D. V. Wiebe
Details
fix (702 bytes, patch)
2007-04-16 23:49 UTC, Eli Fidler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description D. V. Wiebe 2007-04-16 22:50:33 UTC
Version:           1.4.0 (using KDE KDE 3.5.6)
Installed from:    Compiled From Sources
Compiler:          gcc (GCC) 4.1.2 
OS:                Linux

kst crashes when the input data vector to a PSD is changed.

Steps to reproduce:

1. plot a psd
2. right click -> edit plot object
3. edit vector (pops up the Edit Spectrum dialog)
4. change Data Vector to a different vector
5. "OK"

Results:

  kst crashes with console message:

    kst: FATAL: Thread -1239353648 tried to unlock KstRWLock 0x856445c (unlocked) without
         holding the lock

Expected results:

  The PSD is modified to use the newly specified data vector as input.
Comment 1 D. V. Wiebe 2007-04-16 22:56:08 UTC
Created attachment 20291 [details]
backtrace
Comment 2 Netterfield 2007-04-16 23:02:27 UTC
This bug is serious enough to delay 1.4.0 until fixed (if possible).
cbn

On Monday 16 April 2007 4:50:34 pm D.V.Wiebe wrote:
[bugs.kde.org quoted mail]
Comment 3 Eli Fidler 2007-04-16 23:34:24 UTC
It's probably related to the locking changes. I doubt setVector() should be (un)locking the input vector.

I wouldn't be surprised if this also occurs with Spectrograms and Histograms.
Comment 4 Netterfield 2007-04-16 23:47:06 UTC
Can you try to track it down before we release?
> ------- Additional Comments From eli staikos net  2007-04-16 23:34 -------
> It's probably related to the locking changes. I doubt setVector() should be
> (un)locking the input vector.
>
> I wouldn't be surprised if this also occurs with Spectrograms and
> Histograms.

Comment 5 Eli Fidler 2007-04-16 23:49:06 UTC
Created attachment 20292 [details]
fix
Comment 6 Netterfield 2007-04-17 00:11:25 UTC
Any idea why the locks were there in the first place?

cbn
Comment 7 Eli Fidler 2007-04-17 00:46:38 UTC
We used to lock all the inputs and outputs of data objects whenever we locked the object itself. This caused deadlocks and performance issues, so now we only lock the inputs/outputs in update().

Because setVector() was called when the object was locked, the inputs had to be put in a locked state.
Comment 8 Ted Kisner 2007-04-17 08:13:57 UTC
I'm not sure if it is related, but changing the matrix source of an image 
silently fails.  In other words, create 2 matrix objects (say both from 
tests/asciimatrix.txt) and then create an image from matrix #1.  Now go into 
the image dialog and select matrix #2 from the list.  Click OK.  Open the 
image dialog again and...  matrix #1 is still selected!

I guess this probably belongs in a separate bug report...

-Ted


On Monday 16 April 2007 13:50, D.V.Wiebe wrote:
[bugs.kde.org quoted mail]
Comment 9 George Staikos 2007-04-18 03:06:28 UTC
I think this patch is correct.  It should go into trunk, 1.5 branch,  
and I will retag 1.4
--
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/
Comment 10 Andrew Walker 2007-05-08 21:46:32 UTC
Was checked in to 1.5 branch by Eli