Bug #902

RCP: X.X, Java VM memory size arguments

Added by Matthieu Decorde over 9 years ago. Updated almost 5 years ago.

Status:New Start date:07/02/2014
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Démarrage Spent time: -
Target version:TXM X.X

Description

The JVM (and TXM) can refuse to start if the memory size asked is not available (for example, too big for the system).

Solution:
The TXM launcher script must relaunch TXM with another memory setting.
  • TXM must provide a return code:
    • '0' means correct execution, the launcher can quit
    • '1' means bad execution, the launcher must try another memory limit or default memory setting

Further solution: loop by some decrement.

History

#1 Updated by Serge Heiden over 9 years ago

  • Description updated (diff)
  • Category set to Démarrage

#2 Updated by Serge Heiden about 9 years ago

  • Description updated (diff)

#3 Updated by Sebastien Jacquot about 9 years ago

  • Target version changed from TXM 0.7.7 to TXM 0.7.8

#4 Updated by Matthieu Decorde about 8 years ago

  • Target version changed from TXM 0.7.8 to TXM 0.8.0a (split/restructuration)

#5 Updated by Sebastien Jacquot over 5 years ago

  • Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0

#6 Updated by Sebastien Jacquot almost 5 years ago

  • Target version changed from TXM 0.8.0 to TXM X.X

Also available in: Atom PDF