Problem with D2000 HI - after schema is opened, HI stops

Support Forum
#1

Hello
I would like to ask, or I need help what can i do with HI / settings D2000 / OS or I do not know where should be problem. I have many pictures/schemas in application everything working fine, but - after open one specific schema/picture, HI fails with LOG:

Process: HI
** Version: VV12061.061
** Module name: D:\D2000\D2000_EXE\bin\hi.exe
** Module date: 26-10-2018
** Module time: 14:02:02
** Module size: 94267181
** Module loadedAddress: 0x00400000
** Module preferredAddress: 0x00400000
** Uptime: 0 days, 00:00

— Exception information —

Error message: CreateDC_Error 0 The operation completed successfully.

Exception name: SYSTYPES.NULLHANDLE_ERROR
Message: gdilib-dc.adb:182
Call stack traceback locations:
0x0085072D 0x01B8D9B8 0x01AEF1F7 0x010DEADA 0x010D442B 0x010D46C2 0x76416236 0x764168E8 0x76418426 0x7641FDD1 0x764413A7 0x7642B15E 0x010E1831 0x010D442B 0x010D46C2 0x76416236 0x764168E8 0x76417175 0x7641845C 0x776000E4 0x018D63DF 0x01B85D07 0x01AF529B 0x0106631C 0x01068170 0x00F14D26 0x00F16CAF 0x01D9F5CD 0x01D9F0EC 0x01DA04BA 0x010E0D18 0x010D442B 0x010D453B 0x76416236 0x764168E8 0x76417D2F 0x76418110 0x010D35CF 0x010D3468 0x010E9DDE 0x01AC7F0A 0x0040475C 0x004010B4 0x00401126 0x760C3675 0x77629D40 0x77629D13

— Symbolic traceback —

0x85072d in gdilib.dc.createdc at gdilib-dc.adb:182
0x1b8d9b8 in windiatrend.windowresized_msg at windiatrend.adb:2092
0x1aef1f7 in windiatrend.trend.windowresized_msg at windiatrend-trend.adb:67
0x10deada in winlib.window.dispatchmessage at winlib-window.adb:2292
0x10d442b in winlib.window.universaldispatch at winlib-window.adb:715
0x10d46c2 in winlib.window.wnddlgproc at winlib-window.adb:755
0x76416236 in ?? at ??:0
0x764168e8 in ?? at ??:0
0x76418426 in ?? at ??:0
0x7641fdd1 in ?? at ??:0
0x764413a7 in ?? at ??:0
0x7642b15e in ?? at ??:0
0x10e1831 in winlib.window.dispatchmessage at winlib-window.adb:2579
0x10d442b in winlib.window.universaldispatch at winlib-window.adb:715
0x10d46c2 in winlib.window.wnddlgproc at winlib-window.adb:755
0x76416236 in ?? at ??:0
0x764168e8 in ?? at ??:0
0x76417175 in ?? at ??:0
0x7641845c in ?? at ??:0
0x776000e4 in ?? at ??:0
0x18d63df in gc_windiat.resizeitself at gc_windiat.adb:300
0x1b85d07 in windiatrend.initdata at windiatrend.adb:1450
0x1af529b in windiatrend.trend.initdata at windiatrend-trend.adb:433
0x106631c in services.object.createvisualobject_loc at services-object.adb:81
0x1068170 in services.object.msgconnectlist at services-object.adb:240
0xf14d26 in client.messageprocessing at client.adb:1190
0xf16caf in client.messageprocessing at client.adb:1299
0x1d9f5cd in main_window.processkernelmessages.processmessages at main_window.adb:1095
0x1d9f0ec in main_window.processkernelmessages at main_window.adb:1142
0x1da04ba in main_window.posteduser_msg at main_window.adb:1156
0x10e0d18 in winlib.window.dispatchmessage at winlib-window.adb:2495
0x10d442b in winlib.window.universaldispatch at winlib-window.adb:715
0x10d453b in winlib.window.wndproc at winlib-window.adb:731
0x76416236 in ?? at ??:0
0x764168e8 in ?? at ??:0
0x76417d2f in ?? at ??:0
0x76418110 in ?? at ??:0
0x10d35cf in winlib.window.messageloop.userstopmodalloop at winlib-window.adb:567
0x10d3468 in winlib.window.messageloop at winlib-window.adb:585
0x10e9dde in winlib.window.createwindow at winlib-window.adb:3918
0x1ac7f0a in ada_hi at hi.adb:240
0x40475c in main at b~hi.adb:3382
0x4010b4 in <_mingw_CRTStartup> at crt1.c:237
0x401126 in at crt1.c:271
0x760c3675 in ?? at ??:0
0x77629d40 in ?? at ??:0
0x77629d13 in ?? at ??:0

— Process system info —

=================================================
=========== System info : 03.11.18 15:38:32 ===========

Pens nr: 35
Brushes nr: 43
FntStyles nr: 37
FntHwnds nr: 512
Bitmaps nr: 44 / 44 / 211
Pal nr: 75
BmpPal nr: 25
ExtPal nr: 0
StatusTexts nr: 20
RefList nr: 43
Value Cashe - Users nr: 90
Value Cashe - Objects nr: 25
VisualObj nr: 161
DataObj nr: 354
ObjType SYSTEM nr: 2
ObjType PICTURE nr: 90
ObjType GRAPH nr: 71
ObjType ST_TEXT nr: 20
ObjType PALETTE nr: 75
ObjType ALARM nr: 1
ObjType ARCH_VAL nr: 70
ObjType BMPPAL nr: 25

Memory: 184933788
Gnat Memory: 101317916

=================================================
SINGLE MONITOR HI
Num monitors: 1
Monitor size dx/dy: 1280 / 1024

HI is maximized: FALSE
HI client size dx/dy: 1269 / 903
HI pos. dx/dy, rect: 1280 / 1024 ( 0 , 0 , 1280 , 1024 )

Windows version: OS_WIN2008SRVR2
GDI objects: 10000
USER objects: 9995
HandleCount: 543
PageFaultCount: 95745
PeakWorkingSetSize: 322826240
WorkingSetSize: 322826240
QuotaPeakPagedPoolUsage: 627856
QuotaPagedPoolUsage: 626160
QuotaPeakNonPagedPoolUsage: 289896
QuotaNonPagedPoolUsage: 288400
PagefileUsage: 350957568
PeakPagefileUsage: 350957568
PrivateUsage: 350957568
dwMemoryLoad: 18
ullTotalPhys: 12874207232
ullAvailPhys: 10438787072
ullTotalPageFile: 25746448384
ullAvailPageFile: 22875152384
ullTotalVirtual: 4294836224
ullAvailVirtual: 3260108800
ullAvailExtendedVirtual: 0

#2

Problem is : GDI objects: 10000
GDI objects support only one handle per object. Handles to GDI objects are private to a process. That is, only the process that created the GDI object can use the object handle.

There is a theoretical limit of 65,536 GDI handles per session. However, the maximum number of GDI handles that can be opened per session is usually lower, since it is affected by available memory.

There is also a default per-process limit of GDI handles. To change this limit, set the following registry value:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Windows \ GDIProcessHandleQuota
This value can be set to a number between 256 and 65,536.

save as: import.reg and import to reg. + restart PC/NB

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]
“GDIProcessHandleQuota”=dword:0000ffff

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]
“USERProcessHandleQuota”=dword:00004650