|
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 1.0 Transitional//EN"> |
|
2 <html> |
|
3 <head> |
|
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
|
5 <meta http-equiv="Content-Style-Type" content="text/css"> |
|
6 <title>Troubleshooting</title> |
|
7 <link rel="StyleSheet" |
|
8 href="../../../../../../ProfilerActivator/trunk/com.nokia.s60tools.profileractivator.help/book.css" |
|
9 type="text/css"> |
|
10 </head> |
|
11 |
|
12 <body> |
|
13 <h2>Troubleshooting</h2> |
|
14 |
|
15 <p>Below are listed the error messages and resolutions for problems with the PI |
|
16 Import wizard during file import.</p> |
|
17 |
|
18 <table border="1" cellspacing="1" cellpadding="2"> |
|
19 <colgroup><col width="250*"> |
|
20 <col width="356*"> |
|
21 </colgroup> |
|
22 <tbody> |
|
23 <tr> |
|
24 <th>Message</th> |
|
25 <th align="center">Resolution</th> |
|
26 </tr> |
|
27 <tr> |
|
28 <td>Unable to resolve current connection. Please check your connection |
|
29 settings.</td> |
|
30 <td>This message usually appears when you select to get profiler files |
|
31 form device via TraceViewer for the first time, and the connections |
|
32 settings have not yet defined. |
|
33 |
|
34 <p>To resolve the problem, click <strong>Connection |
|
35 Settings...</strong> to open the dialog where you can select the |
|
36 correct settings for the connection you want to use. After saving the |
|
37 settings, click Refresh Plug-ins List and continue with tracing. For |
|
38 more specific instructions, see <a |
|
39 href="../../tasks/analyser/an_load_trace_files.htm">Importing Profiler |
|
40 Data files</a>.</p> |
|
41 </td> |
|
42 </tr> |
|
43 <tr> |
|
44 <td>Could not read available plug-ins from device. See Troubleshooting |
|
45 topic from Help.</td> |
|
46 <td><p>This message appears when the connection settings have been |
|
47 defined, but the information for the plug-in list cannot be fetched.</p> |
|
48 |
|
49 <p>To resolve the problem, test that the Tracing service connection is |
|
50 working:</p> |
|
51 <ol> |
|
52 <li>Click <strong>Connection Settings... </strong></li> |
|
53 <li>Select the connection you are using and click |
|
54 <strong>Edit...</strong></li> |
|
55 <li>Select the <strong>Test Connection</strong> tab</li> |
|
56 <li>Select the Device OS</li> |
|
57 <li>Select Tracing as the service to test</li> |
|
58 <li>Click <strong>Initiate Service Testing</strong>.</li> |
|
59 </ol> |
|
60 |
|
61 <p>If the connection works, but you still get the error message, makes |
|
62 sure that PI Profiler is installed on the device.</p> |
|
63 </td> |
|
64 </tr> |
|
65 <tr> |
|
66 <td>Received corrupted data! See Troubleshooting topic from Help |
|
67 |
|
68 <p></p> |
|
69 </td> |
|
70 <td>This message appears when try to use a USB connections for profiling |
|
71 several plugins, and the connection cannot handle the amount of data. |
|
72 |
|
73 <p>To resolve the problem, try profiling fewer plugins; or, if you need |
|
74 to profile several plugins in the same trace, change to TCP/IP Musti |
|
75 connection. For more specific instructions, see <a |
|
76 href="../../tasks/analyser/an_load_trace_files.htm">Importing Profiler |
|
77 Data files</a>.</p> |
|
78 </td> |
|
79 </tr> |
|
80 <tr> |
|
81 <td>Multiple problems have occurred. Jave heap space.</td> |
|
82 <td>This message can appear when you try to import a large profiler date |
|
83 file. |
|
84 |
|
85 <p>Although Carbide.c++ reserves a large block of memory for the Java |
|
86 Virtual Machine (JVM) to run the whole IDE, in some cases, the trace |
|
87 import process may fail due to out-of-memory situation. This is usually |
|
88 due to the Profiler trace log being too long in time and/or CPU load |
|
89 being extensively high over the use case. The out-of-menory may also |
|
90 lead to instability issues with Carbide itself, in which case the error |
|
91 is shown.</p> |
|
92 |
|
93 <p>This problem can be avoided by keeping the profiled use cases |
|
94 shorter (the recommendation is maximum 5 minutes), and by selecting |
|
95 only those Profiler plug-ins that are needed for analysing the use |
|
96 case. Shorter use cases (in time) and smaller amount of selected |
|
97 profiler plug-ins also ease up the analysis phase, since it is easier |
|
98 to a browse shorter set of data and to pinpoint the possible |
|
99 performance issues within the trace.</p> |
|
100 |
|
101 <p>If you need to analyse longer use cases, there are also other tools |
|
102 available for long-period-testing (LPT). For example, you can run the |
|
103 Nokia Energy Profiler (NEP) directly on target and it can be used for |
|
104 LPT type of use cases.</p> |
|
105 </td> |
|
106 </tr> |
|
107 </tbody> |
|
108 </table> |
|
109 |
|
110 <p></p> |
|
111 |
|
112 <div id="footer"> |
|
113 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights |
|
114 reserved.</div> |
|
115 </body> |
|
116 </html> |