Re: MFC MDI app hangs randomly on some machines, but not others (most are OK). Typical causes?
From: Johan Rosengren (johan.rosengren_at_telia.com)
Date: 05/20/04
- Next message: Brad McMillan: "Re: Implementing a Message Handler for WM_IDLEUPDATECMDUI"
- Previous message: Johan Rosengren: "Re: RICHEDIT 2 in MFC"
- In reply to: coder: "MFC MDI app hangs randomly on some machines, but not others (most are OK). Typical causes?"
- Next in thread: coder: "Re: MFC MDI app hangs randomly on some machines, but not others (most are OK). Typical causes?"
- Reply: coder: "Re: MFC MDI app hangs randomly on some machines, but not others (most are OK). Typical causes?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 May 2004 16:04:21 +0200
coder,
If the problem is reproducible on the problematic machines, that is, the
same file always hang on machine X, but not on Y and Z, you will probably
have to find *and* not all files give problems on X, you'll have to analyze
the difference between the data files to get further. From what I understand
from your post, this is not the case however. You might want to use the age
old method of adding logging code to your app, perhaps activated by a flag.
Then you will have a chance to diagnose where in code the hang occurs, and
will have a much better chance of catching the problem.
Machine dependent problems I've been through during my days as a developer
includes non-initialized double class members (resulting in a crash on some
processors) and differences in graphics card drivers (handling coordinate
overflow differently).
Johan Rosengren
Abstrakt Mekanik AB
"coder" <googlecoder@yahoo.com> a écrit dans le message de
news:bfcb891f.0405190957.3a02976d@posting.google.com...
> Please advise.
>
> On rare occasions, users of our MFC MDI app have found that the
> program hangs when opening files (our own custom file types).
> However, we have been unable to recreate the problem during extensive
> testing (98/SE,ME,XP,2000), making it hard to track down.
>
> It seems that two identical machines (OS, dll versions and spec) can
> behave quite differently with exactly the same app and file to open -
> only the hardware is different. In testing, clean installations of all
> major Windows operating systems have failed to reproduce the bug.
>
> It seems that all of the crashes occur on Win 98/ME, though we have
> many users of these OSs who have not encountered any problems. Most
> systems which have encountered the bug have been of HIGHER spec
> (memory/processor/disk) than the slowest sytems tested by us, so it
> does not look like a plain system resource issue. The app is
> installed on many hundreds of machines, and is operating OK.
>
> DLL versioning (eg comctl) has been checked and shown to be OK in many
> of the problem cases. The MFC dlls are statically linked to the app.
> One other custom dll is distributed and stored locally with the app.
>
> The crash always occurs during the file open process, not during app
> launch. Unfortunately we are unable to catch the crash in a debugging
> environment (as we cannot reproduce the bug in test).
>
> So the question is... are there any *typical causes* of problems which
> result in this kind of inconsistent behaviour across systems? I have
> read that video card acceleration may be to blame... but other
> thoughts much appreciated.
>
> Thanks. All help gratefully received.
- Next message: Brad McMillan: "Re: Implementing a Message Handler for WM_IDLEUPDATECMDUI"
- Previous message: Johan Rosengren: "Re: RICHEDIT 2 in MFC"
- In reply to: coder: "MFC MDI app hangs randomly on some machines, but not others (most are OK). Typical causes?"
- Next in thread: coder: "Re: MFC MDI app hangs randomly on some machines, but not others (most are OK). Typical causes?"
- Reply: coder: "Re: MFC MDI app hangs randomly on some machines, but not others (most are OK). Typical causes?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
