bugGNU Octave - Bugs: bug #51845, Variable editor: trying to open...

 
 

bug #51845: Variable editor: trying to open Java or COM objects leads to infinite loop & crash

Submitter:  Philip Nienhuis <philipnienhuis>
Submitted:  Fri 25 Aug 2017 01:36:53 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Fixed Assigned to:  None
Originator Name:  Philip Nienhuis Open/Closed:  * Closed
Release:  * dev Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 22 Apr 2018 07:57:20 PM UTC, comment #2: 

This bug has been fixed in the dev version somewhere in the last months.

Closing report.

Philip Nienhuis <philipnienhuis>
Group Member
Fri 25 Aug 2017 01:48:33 PM UTC, comment #1: 

Turns out I investigated classdef objects display in the variable Editor before and they behave more or less like structs there.

So this bug is rather about Java (and COM) objects.

Philip Nienhuis <philipnienhuis>
Group Member
Fri 25 Aug 2017 01:36:53 PM UTC, original submission:  

Provisionally only Windows but I think this also happens on Linux.

Steps to reproduce:

a = javaObject ("java.lang.Double", 1.5);

##right-click a in workspace, or do
openvar (a)

and in the command window we get an endless loop of

:
>> error: [java] java.lang.IllegalArgumentException: not a Java array
error: parse error
>> error: [java] java.lang.IllegalArgumentException: not a Java array
error: parse error
>> error: [java] java.lang.IllegalArgumentException: not a Java array
error: parse error
:


Ctrl-C doesn't help (reliably). Closing Octave's GUI using the close button does, but then Octave crashes upon exit.

Similar behavior goes to COM objects (in Windows).

I haven't tried this with other objects (classdef etc.) but I suspect there it will also go wrong.

When the variable Editor was still just a patch I thought that limiting the function openvar (that is called when right-clicking & selecting "Open in Variable Editor" in the workspace) to only accept some types of variables (prvisionally just numeric, cell, text and struct) would be the best option to avoid this bug.  Later on when the variable Editor could handle more types openvar could be adapted accordingly.
But I couldn't find out how to get this together (due to lacking C++/Qt skills).

Philip Nienhuis <philipnienhuis>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by philipnienhuis (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-04-22 philipnienhuis StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code