|
|
|
|
|
|
|
|
| Re: Eclipse Titan hangs due to waiting user operation [message #1747026 is a reply to message #1746990] |
Tue, 08 November 2016 15:50   |
 Michael Josenhans
Messages: 99
Registered: February 2016 |
Member |
|
|
> Could you please check the output on your debug console, to see what the Designer tries to re-analyze after these changes?
On my machine it only needs to re-check the file changed .. maybe we misscalculate something there.
This is the console output. (I do not have any special debug console):
TTCN-3 and ASN.1 Compiler for the TTCN-3 Test Executor
Product number: CRL 113 200/5 R5A
Build date: Aug 1 2016 18:50:42
Compiled with: GCC 5.4.0
Copyright (c) 2000-2016 Ericsson Telecom AB
Operation finished successfully.
>Could you check if you are running low on memory in eclipse?
The memory usage grows from maybe 89 MB to 215 MB (of 256 MB).
Then it drops back to 89 MB and grows again ....
The text besides always tells 'Analyzing the source code (0%)'
[Updated on: Tue, 08 November 2016 15:56] Report message to a moderator |
|
|
|
| Re: Eclipse Titan hangs due to waiting user operation [message #1747102 is a reply to message #1747031] |
Wed, 09 November 2016 13:17 |
|
Hi Michael,
I have the impression that you allocate too little memory for Eclipse;
please check par. 5.2 of the Eclipse install guide:
5.2 Configuring Java
You might need to modify your eclipse.ini file (usually located in the same directory as your eclipse executable.)
It is suggested to have at least 1GB and recommended 2 GB free memory per 1 million TTCN-3/ASN.1 source code lines (but it strongly depends on the code complexity). In Java it is controlled via the Xmx option.
For example, if Java 1.6 or 1.7 is applied and a project of 2 million TTCN-3 code lines is edited, the suggested settings in eclipse.ini are these:
-vmargs
-XX:MaxPermSize=2048M
-Dosgi.requiredJavaVersion=1.7
-Xms1024M
-Xmx4g
If Java 1.8 is used then MaxPermSize is ignored, its support is removed. Use these settings instead:
-vmargs
-Dosgi.requiredJavaVersion=1.8
-XX:+UseG1GC
-Xms1024M
-Xmx4g
Notes:
If you cannot edit the eclipse.ini file, you can start eclipse with flags. For example
eclipse vmargs -Xmx4g
modifies the maximum memory allocation for the virtual machine.
Please try to increase allocated memory in eclipse.ini
You don't have a lot of code but 256M sounds insufficient.
BR
Elemer
|
|
|
| Re: Eclipse Titan hangs due to waiting user operation [message #1747200 is a reply to message #1747102] |
Thu, 10 November 2016 16:44 |
Michael Josenhans
Messages: 99
Registered: February 2016 |
Member |
|
|
Ok. Here is the debug output:
On-the-fly analyzation of project titan.TestPorts.SocketCANasp started
**It took 3.426012414 seconds till the files (23 pieces) of project titan.TestPorts.SocketCANasp got syntactically analyzed
**Selection with Broken parts via references is started at: 2016.11.10 05:41:35.848
** Module SocketCAN__Templates can not be skipped as it was not yet analyzed.
** Module Isobus can not be skipped as it was not yet analyzed.
** Module Isotptest can not be skipped as it was not yet analyzed.
** Module IsobusMessageTypes can not be skipped as it was not yet analyzed.
** Module IsobusCMMessageTypes can not be skipped as it was not yet analyzed.
** Module Raw can not be skipped as it was not yet analyzed.
** Module Isobustest can not be skipped as it was not yet analyzed.
** Module SocketCAN__BCM__test can not be skipped as it was not yet analyzed.
** Module Bcm can not be skipped as it was not yet analyzed.
** Module SocketCAN__PortType can not be skipped as it was not yet analyzed.
** Module J1939 can not be skipped as it was not yet analyzed.
** Module Can can not be skipped as it was not yet analyzed.
** Module SocketCAN__RAW__test can not be skipped as it was not yet analyzed.
** Module test2 can not be skipped as it was not yet analyzed.
** Module test3 can not be skipped as it was not yet analyzed.
** Module SocketCANtest can not be skipped as it was not yet analyzed.
** Module IsobusNMMessageTypes can not be skipped as it was not yet analyzed.
** Module IsobusVTMessageTypes can not be skipped as it was not yet analyzed.
** Module CanError can not be skipped as it was not yet analyzed.
** Module Isotp can not be skipped as it was not yet analyzed.
** Module General__Types can not be skipped as it was not yet analyzed.
** Module SocketCAN__Types can not be skipped as it was not yet analyzed.
** Module Isobus__Templates can not be skipped as it was not yet analyzed.
**Selection with Broken parts via references is ended at: 2016.11.10 05:41:35.862
**Selection time is: 0.013229685000000001 seconds (13229685 nanoseconds).
**Nr. of broken modules: 23
**Broken modules name: [module: SocketCAN__Templates, module: Isobus, module: Isotptest, module: IsobusMessageTypes, module: IsobusCMMessageTypes, module: Raw, module: Isobustest, module: SocketCAN__BCM__test, module: Bcm, module: SocketCAN__PortType, module: J1939, module: Can, module: SocketCAN__RAW__test, module: test2, module: test3, module: SocketCANtest, module: IsobusNMMessageTypes, module: IsobusVTMessageTypes, module: CanError, module: Isotp, module: General__Types, module: SocketCAN__Types, module: Isobus__Templates]
** Had to start checking at 23 modules.
**On-the-fly semantic checking of projects (23 modules) took 0.730165546 seconds
The whole analysis block took 4.261023067 seconds to complete
On-the-fly analyzation of project titan.TestPorts.SocketCANasp started
** Had to start checking at 0 modules.
**On-the-fly semantic checking of projects (23 modules) took 2.81321E-4 seconds
The whole analysis block took 0.0026314100000000003 seconds to complete
**It took 0.045728091000000005 seconds till the files (22 pieces) of project titan.TestPorts.SocketCANasp got syntactically analyzed
The whole analysis block took 0.049333578 seconds to complete
**It took 0.111342092 seconds till the files (22 pieces) of project titan.TestPorts.SocketCANasp got syntactically analyzed
The whole analysis block took 0.11174542500000001 seconds to complete
**It took 0.102277881 seconds till the files (22 pieces) of project titan.TestPorts.SocketCANasp got syntactically analyzed
The whole analysis block took 0.102750357 seconds to complete
**It took 0.054393090000000005 seconds till the files (22 pieces) of project titan.TestPorts.SocketCANasp got syntactically analyzed
The whole analysis block took 0.054744182 seconds to complete
**It took 0.064461828 seconds till the files (22 pieces) of project titan.TestPorts.SocketCANasp got syntactically analyzed
The whole analysis block took 0.065253689 seconds to complete
**It took 0.09879035600000001 seconds till the files (22 pieces) of project titan.TestPorts.SocketCANasp got syntactically analyzed
The whole analysis block took 0.099098984 seconds to complete
> Window/Preferences/ TITAN Preferences/On-the-fly checker and disable the option "Warn and disable parsing before the system runs out of memory".
There is no such preferences option in my Titan preferences tab. The option "Treat on-the -fly error as fatal for the build was not activated. See attachment.
When activation above option nothing changes. See attachment.
[Updated on: Thu, 10 November 2016 17:13] Report message to a moderator |
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03434 seconds
] 
Search
Help
Register
Login
Home
