Prev: mp3 edit function
Next: using process.start to open a web page
From: tclancey on 5 Jul 2008 13:43
Hi, I'm having a problem with an installed application, apparently the PC
locks solid from time to time, seems to be random, but after the lock the
following can be found in the application events.

Faulting application my-application.exe, version 1.0.0.0, stamp 463070d8,
faulting module gdi32.dll, version 5.1.2600.3099, stamp 45f03054, debug? 0,
fault address 0x0003cbd4.

Then also get the following when adding a new converter (see below) to the
system.

Hanging application my-application.exe, version 1.0.0.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.

Does anyone know, is this a problem with the application I've written, or is
the GDI the problem?

The application isn't graphical, the main form simply holds a grid of
information. The app pulls data in from several virtual com ports
(RS232/Ethernet converters) and also sends data to various Serial printers,
through the same adapters. The app also sends and receives data to/from
several small hmi displays.

I believe the GDI handles 2d graphics and has a lot to do with printing? In
the course of say, 24 hours, the application is sending a lot of print jobs,
but I have other applications running at different customers doing a lot
more without problems.

Any ideas or information would be really helpful, everything I've found on
the web about this kind of lock points towards other applications causing
the system to hang. Hopefully I will have a hijackthis report from the
customer on Monday, but I don't expect that to show anything unusual.

Thanks.


From: kimiraikkonen on 5 Jul 2008 16:40
On Jul 5, 8:43 pm, "tclancey" <t...(a)idcodeware.co.uk> wrote:
> Hi, I'm having a problem with an installed application, apparently the PC
> locks solid from time to time, seems to be random, but after the lock the
> following can be found in the application events.
>
> Faulting application my-application.exe, version 1.0.0.0, stamp 463070d8,
> faulting module gdi32.dll, version 5.1.2600.3099, stamp 45f03054, debug? 0,
> fault address 0x0003cbd4.
>
> Then also get the following when adding a new converter (see below) to the
> system.
>
> Hanging application my-application.exe, version 1.0.0.0, hang module
> hungapp, version 0.0.0.0, hang address 0x00000000.
>
> Does anyone know, is this a problem with the application I've written, or is
> the GDI the problem?
>
> The application isn't graphical, the main form simply holds a grid of
> information. The app pulls data in from several virtual com ports
> (RS232/Ethernet converters) and also sends data to various Serial printers,
> through the same adapters. The app also sends and receives data to/from
> several small hmi displays.
>
> I believe the GDI handles 2d graphics and has a lot to do with printing? In
> the course of say, 24 hours, the application is sending a lot of print jobs,
> but I have other applications running at different customers doing a lot
> more without problems.
>
> Any ideas or information would be really helpful, everything I've found on
> the web about this kind of lock points towards other applications causing
> the system to hang. Hopefully I will have a hijackthis report from the
> customer on Monday, but I don't expect that to show anything unusual.
>
> Thanks.

I can't do more than guessing with such information you posted, but
based on my wild guess, it may be a "timing" issue, that is, when your
application is doing serial communication synchronously, maybe your
form (UI) or an object which is related to "system.drawing" may get
blocked, then your application may crash.

You'd better use try-catch blocks and handle exceptions with message
including stacktrace information, then maybe they may route you to a
right direction to solve the problem.

Sorry nothing more than guessing.

Thanks,

Onur Güzel
From: Brian Gideon on 6 Jul 2008 21:52
On Jul 5, 12:43 pm, "tclancey" <t...(a)idcodeware.co.uk> wrote:
> Hi, I'm having a problem with an installed application, apparently the PC
> locks solid from time to time, seems to be random, but after the lock the
> following can be found in the application events.
>
> Faulting application my-application.exe, version 1.0.0.0, stamp 463070d8,
> faulting module gdi32.dll, version 5.1.2600.3099, stamp 45f03054, debug? 0,
> fault address 0x0003cbd4.
>
> Then also get the following when adding a new converter (see below) to the
> system.
>
> Hanging application my-application.exe, version 1.0.0.0, hang module
> hungapp, version 0.0.0.0, hang address 0x00000000.
>
> Does anyone know, is this a problem with the application I've written, or is
> the GDI the problem?
>
> The application isn't graphical, the main form simply holds a grid of
> information.  The app pulls data in from several virtual com ports
> (RS232/Ethernet converters) and also sends data to various Serial printers,
> through the same adapters.  The app also sends and receives data to/from
> several small hmi displays.
>
> I believe the GDI handles 2d graphics and has a lot to do with printing?  In
> the course of say, 24 hours, the application is sending a lot of print jobs,
> but I have other applications running at different customers doing a lot
> more without problems.
>
> Any ideas or information would be really helpful, everything I've found on
> the web about this kind of lock points towards other applications causing
> the system to hang.  Hopefully I will have a hijackthis report from the
> customer on Monday, but I don't expect that to show anything unusual.
>
> Thanks.

That looks like an unmanaged crash. I can't say definitely, but that
does make it less likely that it was caused by your code. Now, that
does not mean that your code did not somehow contribute to the
problem. It's just that an unmanaged crash is not suppose to happen
no what your code is doing unless there is a bug in some unmanaged
portion of the application. You need to get a crash dump of the fault
and examine the stack trace. The problem may not necessarily be with
GDI. It may be some other layer using the gdi32.dll API incorrectly.
From: tclancey on 7 Jul 2008 05:33
Thanks for your feedback guys, this is more or less what I was thinking.
There are very few parts of the application that are not handled. I'll
secure those and see what we get.

Thanks again.


"tclancey" <tull(a)idcodeware.co.uk> wrote in message
news:e8HUhas3IHA.3348(a)TK2MSFTNGP03.phx.gbl...
> Hi, I'm having a problem with an installed application, apparently the PC
> locks solid from time to time, seems to be random, but after the lock the
> following can be found in the application events.
>
> Faulting application my-application.exe, version 1.0.0.0, stamp 463070d8,
> faulting module gdi32.dll, version 5.1.2600.3099, stamp 45f03054, debug?
> 0, fault address 0x0003cbd4.
>
> Then also get the following when adding a new converter (see below) to the
> system.
>
> Hanging application my-application.exe, version 1.0.0.0, hang module
> hungapp, version 0.0.0.0, hang address 0x00000000.
>
> Does anyone know, is this a problem with the application I've written, or
> is the GDI the problem?
>
> The application isn't graphical, the main form simply holds a grid of
> information. The app pulls data in from several virtual com ports
> (RS232/Ethernet converters) and also sends data to various Serial
> printers, through the same adapters. The app also sends and receives data
> to/from several small hmi displays.
>
> I believe the GDI handles 2d graphics and has a lot to do with printing?
> In the course of say, 24 hours, the application is sending a lot of print
> jobs, but I have other applications running at different customers doing a
> lot more without problems.
>
> Any ideas or information would be really helpful, everything I've found on
> the web about this kind of lock points towards other applications causing
> the system to hang. Hopefully I will have a hijackthis report from the
> customer on Monday, but I don't expect that to show anything unusual.
>
> Thanks.
>


 | 
Pages: 1
Prev: mp3 edit function
Next: using process.start to open a web page