Bug #2751

Some RCP platform errors are not shown in TXM

Added by Sebastien Jacquot 9 months ago. Updated 9 months ago.

Status:New Start date:01/30/2020
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Logs Spent time: -
Target version:TXM 0.8.2

Description

Some RCP platform errors are not shown in TXM.
E.g. some UI Widget errors, infinite loop errors, thread access, etc. are caught by the RCP manager and not displayed in the console.
These errors are logged in file but also dedicated to be shown in the Error Log view of Eclipse but we do not embed it in TXM.
So a TXM session can be corrupted, e.g. a R communication problem leading to infinite loop because of an out of memory but the user (or debugger) has no feedback.

Solution 1

  • add Error Log view to TXM product
  • verify that when an error occurs the view is automatically opened as in Eclipse IDE

Solution 2

  • add -consoleLog to TXM product
  • verify that when an error occurs it is well displayed in the TXM console (and not in launching terminal, e.g. the windows command of TXM.bat)

NOTE: for same purpose of debugging and feedback, it would be nice to activate the red color for System.err in TXM console.

LOG for an encountered non-displayed Java Heap Space error:

Caused by: java.lang.OutOfMemoryError: Java heap space
    at org.rosuda.REngine.Rserve.protocol.RTalk.request(RTalk.java:218)

After that R becomes inaccessible but the user is not alerted.

History

#1 Updated by Sebastien Jacquot 9 months ago

  • Description updated (diff)

#2 Updated by Sebastien Jacquot 9 months ago

  • Description updated (diff)

#3 Updated by Sebastien Jacquot 9 months ago

  • Target version changed from TXM 0.8.1 to TXM 0.8.2

Also available in: Atom PDF