[kepler-dev] [Bug 5412] saving with an open plot window crashes

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5412

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
       Hours Worked|                            |0.15
             Status|NEW                         |ASSIGNED
                 CC|                            |cxh at eecs.berkeley.edu

--- Comment #1 from Christopher Brooks <cxh at eecs.berkeley.edu> 2011-05-26 15:30:12 PDT ---
I checked in a change to ptolemy.plot.Plot, but I can't verify
that the problem is fixed in Kepler because Kepler does not build
in a fresh tree for me.

Before the change, I could not replicate the problem in Ptolemy.
I ran
$PTII/bin/vergil ~/ptII/ptolemy/domains/sdf/demo/Butterfly/Butterfly.xml
and then tried to save the model.

When you say "Kepler crashes", do you mean that the Kepler process exits
or do you mean that you get a stack trace?

If Kepler crashes, then there is a more substantial problem that should be
fixed.

I temporarily modified ptolemy/plot/Plot.java to always throw an
exception:

    /** Write plot format information to the specified output stream in         
     *  PlotML, an XML scheme.                                                  
     *  @param output A buffered print writer.                                  
     */
    public synchronized void writeFormat(PrintWriter output) {
        super.writeFormat(output);

    if (1==1) {
            throw new RuntimeException("Test for internal error while
writing");
    }

When I run the above veril command, I can try to save the plot or the model
and I get a stack trace in both situations, but Vergil stays running.

Could you make a similar change to the Plot.java file in Kepler and
verify that Kepler remains running even if there is an exception?

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.