search

mspapant / gdipp

Automatically exported from code.google.com/p/gdipp
0 stars 0 forks source link

Outlook 2003 fails to start with 'out of memory' message #83

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Which program triggers the problem? Specify the filename if possible.
Microsoft Outlook 2003

What steps will reproduce the problem?
1.Boot the PC
2.Start Outlook 2003
3.Outlook fails with error message - no memory/resources
4.Start Outlook 2003 again
5.Program starts successfully

What is the expected output? What do you see instead?
The first time Outlook 2003 is started once the PC has been booted it will fail 
with an out of memory/resources message (see attachment for screenshot of 
dialog box. Retrying Outlook results in a successful start of the program. 
Subsequent closures and restarts of Outlook are all successful - it is only the 
first time the program is called that it fails.  

What version of gdipp (including renderer)? On which operating system?
The problem has ocurred on 7.6 and 8.1 of gdipp. I'm running Windows 7 Pro 32 
bit (Core i7 860 with 4Gb).

Please provide any additional information below. Screenshots always help.

Original issue reported on code.google.com by stevedav...@gmail.com on 2 Jul 2010 at 8:34

Attachments:

GoogleCodeExporter commented 8 years ago 
You are the first one reporting memory/resource problem. I need more 
information about this issue. Does this problem only occur in Outlook 2003? If 
you can, please use Process Explorer 
(http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) to find out 
which resource is leaking, memory or GDI object.

Original comment by crendk...@gmail.com on 2 Jul 2010 at 3:59

GoogleCodeExporter commented 8 years ago 
This user isn't alone. I've had the same issue. Outlook 2003 will sometimes 
start up just fine. At other times, however, I'll get the same Out of Memory 
error reported by the original poster. If I likewise try restarting Outlook one 
or more times, it will eventually run. (It usually doesn't take more than two 
subsequent restarts to get it to open properly.)

In my experience, the problem seems to happen after the system has been running 
for a while. For example, I don't recall any case in which Outlook failed to 
start up following a fresh reboot. If I wait a few hours, however, and try to 
launch Outlook, I'll sometimes get the problem cited above.

Confirmed on two systems, both running Windows Vista Ultimate Edition x64 SP2. 
One system is an AMD64-based desktop, the other a Core2 Duo laptop.

This is specific to gdipp 7.6 only. I've had bad luck with 8.1 and have stayed 
put on 7.6. Can't confirm on any other versions.

I'll likewise try to report back with the info you requested, re: 
ProcessExplorer.

Original comment by uli.kun...@gmail.com on 7 Jul 2010 at 4:57

GoogleCodeExporter commented 8 years ago 
Updated, with a fresh screenshot. Same thing, ya see? :)

Original comment by uli.kun...@gmail.com on 7 Jul 2010 at 5:01

Attachments:

GoogleCodeExporter commented 8 years ago 
Firstly apologies for the delay, but I've been too busy to check back recently. 
I've loaded Process Explorer, but not being a PC developer, I'm not exactly 
sure what you want to see. Attached are 3 snapshots of the screen. The first 
(before.jpg) is the system before I started Outlook. The second (after.jpg) is 
after Outlook has crashed and is currently showing the dialog box. The third 
(after2.jpg) is a 'threads' tab on the Outlook properiies dialog in Process 
Explorer.

Steve.

Original comment by stevedav...@gmail.com on 8 Jul 2010 at 8:32

Attachments:

GoogleCodeExporter commented 8 years ago 
Ah, I didn't answer your first question. Yes this seems to only occur in 
Outlook 2003, however very rarely Explorer fails to start when Windows 7 boots 
- this may be completely unrelated, but Windows 7 has always booted 100% before 
I installed Gdipp. The failure is so rare (once every 2 weeks to a month) that 
it's hard to pin down, or to definately say that this is the fault of gdipp.

Steve.

Original comment by stevedav...@gmail.com on 8 Jul 2010 at 8:40

GoogleCodeExporter commented 8 years ago 
I'm sorry I forgot this issue for such a long time. Have you got any luck with 
the recent versions?

Original comment by crendk...@gmail.com on 18 Sep 2010 at 5:37

GoogleCodeExporter commented 8 years ago 
Hi, I've just installed the latest beta (0.9.1 32bit) and the problem no longer 
occurs. It looks like you've squashed the bug. Thanks.

Steve.

Original comment by stevedav...@gmail.com on 24 Sep 2010 at 4:36

GoogleCodeExporter commented 8 years ago 
Good to hear that. I understand this is a non-deterministic problem that might 
regress in the future. Report and open the issue again if you experience that. 
Thank you!

Original comment by crendk...@gmail.com on 24 Sep 2010 at 8:52