Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

GDI-Error with Preview

edited June 2010 in General
Hi!

I am using the latest RB (12.0 Build 161) with Delphi 7. One of our customers is getting the following error when previewing a report:

-----------------------------
exception number : 2
exception class : EOutOfResources
exception message : Für diesen Befehl ist nicht genügend Speicher verfügbar.

Main ($be0):
0044364b +077 Winmgm.exe Graphics GDIError
00443683 +007 Winmgm.exe Graphics GDICheck
0044768f +117 Winmgm.exe Graphics CopyBitmap
0044804b +063 Winmgm.exe Graphics TBitmap.CopyImage
004497b4 +03c Winmgm.exe Graphics TBitmap.SetWidth
00aae159 +179 Winmgm.exe ppViewr 1920 +36 TppScreenDevice.CalculateScaledPageSize
00aadcd8 +038 Winmgm.exe ppViewr 1794 +15 TppScreenDevice.RenderFullBlankPage
00aadad8 +09c Winmgm.exe ppViewr 1726 +17 TppScreenDevice.RenderPage
00aad7b8 +194 Winmgm.exe ppViewr 1579 +35 TppScreenDevice.ReceivePage
00adcfb2 +0c2 Winmgm.exe ppDevice 946 +26 TppPublisher.TakeDeviceAction
00add29b +01b Winmgm.exe ppDevice 1171 +6 TppPublisher.ReceivePage
00a42965 +019 Winmgm.exe ppReport 2071 +2 TppReport.PageSent
00a957a4 +018 Winmgm.exe ppClass 10045 +1 TppCustomEngine.DoOnPageSent
00a30707 +1b7 Winmgm.exe ppEngine 1765 +33 TppEngine.SendPage
00a30121 +175 Winmgm.exe ppEngine 1537 +65 TppEngine.FinishPage
00a2f079 +1c1 Winmgm.exe ppEngine 729 +76 TppEngine.GeneratePage
00a2f1ca +0e6 Winmgm.exe ppEngine 814 +52 TppEngine.RestorePage
00a2ed3c +04c Winmgm.exe ppEngine 562 +25 TppEngine.Generate
00a2ec31 +0e9 Winmgm.exe ppEngine 501 +30 TppEngine.RequestPage
00a42834 +0e0 Winmgm.exe ppReport 1993 +25 TppReport.RequestPage
00add3fc +044 Winmgm.exe ppDevice 1248 +11 TppPublisher.DoOnPageRequest
00add1b3 +063 Winmgm.exe ppDevice 1058 +16 TppPublisher.Publish
00ad6139 +009 Winmgm.exe ppProd 1452 +1 TppProducer.PublishReport
00ad61ea +052 Winmgm.exe ppProd 1516 +10 TppProducer.PrintToDevices
00a42719 +085 Winmgm.exe ppReport 1953 +19 TppReport.PrintToDevices
00ad6fac +01c Winmgm.exe ppProd 2176 +8 TppProducer.PreviewFormActivateEvent
009f99c7 +02b Winmgm.exe ppForms 600 +6 TppForm.ehTimer_Notify
0045e873 +00f Winmgm.exe ExtCtrls TTimer.Timer
0045e757 +02b Winmgm.exe ExtCtrls TTimer.WndProc
0043f22c +014 Winmgm.exe Classes StdWndProc
7e3696c2 +00a user32.dll DispatchMessageA
004dddf7 +083 Winmgm.exe Forms TApplication.ProcessMessage
004dde2e +00a Winmgm.exe Forms TApplication.HandleMessage
004da5b5 +15d Winmgm.exe Forms TCustomForm.ShowModal
009f9ad6 +01a Winmgm.exe ppForms 676 +10 TppForm.ShowModal
00ad62f7 +05f Winmgm.exe ppProd 1627 +23 TppProducer.PrintToScreen
00ad6034 +050 Winmgm.exe ppProd 1394 +12 TppProducer.Print
00a41863 +027 Winmgm.exe ppReport 1059 +7 TppReport.Print
022d64ee +e6e Winmgm.exe gfdru 2586 +224 TGFDrucken.bStartDruckClick
022d8040 +6c4 Winmgm.exe gfdru 2888 +96 TGFDrucken.Druck
022d7952 +026 Winmgm.exe gfdru 2778 +3 TGFDrucken.DoPreview
02349212 +1ea Winmgm.exe dm_Ec3 4852 +33 TdmEC3.DruckDenGf
-----------------------------

The report isn't very big, only one or two pages, no graphics. And it seams that it only occurs when the user is maximizing the preview-window. Do you have any
ideas what this can be? It is only one customer of many and the error is not here on my side to rebuild, so debugging is not possible.
Thank you.

Gruß aus den Bergen
Günter

Comments

  • edited June 2010

    I recommend running the application using a tool that can check for
    memory/resource leaks. AQTime and FastMM are two such tools we use here.

    Ask the customer to shut down the application, run it again and test the
    preview. Does the error occur then? Or only after the application has been
    running for a while?



    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com



    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited June 2010
    In article <4c0923b1@mail.>, Nard Moseley (Digital Metaphors) wrote:

    We are using FastMM and don't detect any significant Leaks (just the one from
    Indy)


    It is also coming when he starts the application and make a maximized
    preview. For now the customer is avoiding to make preview, but thats not a
    good solution.

    I just would need a hint where I can search for the error, I don't think it
    is with RB, but maybe graphic card, virusscanner or printer driver. The bad
    thing is, that the customer is 5 hours away from us ...


    Gruß aus den Bergen
    Günter
  • edited June 2010
    Hi,
    had the same troubles but with other VCL-components. This is due to a
    small sizing in registry concerning GDI-handles. Just put the following
    lines into a .reg-file and install it on the workstation.


    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
    Manager\Memory Management]
    "SessionViewSize"=dword:00000080
    "SessionPoolSize"=dword:00000040

    Regards

    Toni


    Am 04.06.2010, 11:39 Uhr, schrieb Günter Kieninger :



    --
    Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
  • edited June 2010
    Hi Toni!
    In article , Toni
This discussion has been closed.