View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001334 | JEDI VCL | 00 JVCL Components | public | 2004-02-16 17:19 | 2004-03-09 02:47 |
| Reporter | dbbolm123 | Assigned To | remkobonte | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Summary | 0001334: TJvTrayIcon; TJvFormPlacement imcompatible with approx 10% of Win XP machines | ||||
| Description | D5 and D7. If JvTrayIcon or JvPlacement files are just included (let alone used) in a unit, the application will raise an exception during the INITIALIZATION of the application. This occurs in about 10% of the XP machines tested. I don't have time to trace it, but I think that something in an initialization section of one of the units is raising an exception (the generic xp send error message). In the case of the TJvFormPlacement, I was able to revert the application back to D5, and use the RxLib TFormPlacement instead to elimiate the problem. There are other Jedi components that seem to have this same problem, but these are two that I have definitely tracked down and replaced to move forward. | ||||
| Tags | No tags attached. | ||||
|
|
I don't have XP, so I can't test but it seems the only thing they have in common is that the use window hooking from JvWndProcHook.pas... |
|
|
I think it's the famous JCL hyper-threading bug, see 0001023. edited on: 02-17-04 07:00 |
|
|
>>I think it's the famous JCL hyper-threading bug, see 0001023. I updated the JvComputerInfo.pas as instructed and recompiled the packages, but have the same results. I did some further testing and found the following...I don't know if this helps. Created a small test app that contains only a TJvTrayIcon and a popupmenu. Put the exe in a folder, and closed the folder. Then, opened the folder and double clicked on the app. The first time it will raise an exception. After that, it will launch ok from there. If you close the folder and then reopen, it will raise an exception again the first time, but is ok there after? If the app is put in the Run/RunOnce or the startup group, it will raise an exception every time when re-booting (my apps case). |
|
|
JvComputerInfo.pas? The hyper-threading bug is in JclSysInfo.pas. You can check if it is this bug by removing the GetCpuInfo call in the SetupFunctions procedure in JclGraphUtils.pas. If this removes the error then you have 3 options: * upgrade JCL to JCL 1.9 * wait for JVCL 3.0 that will include JCL 1.9 * adjust the GetCpuInfo function in JclSysInfo.pas by yourself. If removing the GetCpuInfo call does not remove the bug, then make a small application that reproduces the bug and post it here as attachment. edited on: 02-17-04 09:36 |
|
|
remkobonte...thank you. You were dead on. This is the same problem in 0001023. Sorry for the misunderstanding...busy morning. I will make the changes you suggest, and you can close this thread. Thanks again for the prompt response. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-02-16 17:19 | dbbolm123 | New Issue | |
| 2004-02-17 05:42 |
|
Note Added: 0002960 | |
| 2004-02-17 05:43 |
|
Status | new => feedback |
| 2004-02-17 06:56 | remkobonte | Note Added: 0002961 | |
| 2004-02-17 07:00 | remkobonte | Note Edited: 0002961 | |
| 2004-02-17 08:32 | anonymous | Note Added: 0002962 | |
| 2004-02-17 09:35 | remkobonte | Note Added: 0002964 | |
| 2004-02-17 09:36 | remkobonte | Note Edited: 0002964 | |
| 2004-02-17 10:06 | dbbolm123 | Note Added: 0002968 | |
| 2004-02-17 10:27 | remkobonte | Status | feedback => resolved |
| 2004-02-17 10:27 | remkobonte | Resolution | open => duplicate |
| 2004-02-17 10:27 | remkobonte | Relationship added | duplicate of 0001023 |
| 2004-02-17 10:27 | remkobonte | Assigned To | => remkobonte |
| 2004-03-09 02:47 |
|
Status | resolved => closed |
