https://bugs.winehq.org/show_bug.cgi?id=50369
Bug ID: 50369
Summary: Multiple tools for viewing GDI handles/resources list
and GDI leak detection require support for
PEB->GdiSharedHandleTable (GDIView, GDILeaks)
Product: Wine
Version: 6.0-rc3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
as it says. I know this information can be retrieved tracing processes with
Wine 'gdi' debug channel.
https://source.winehq.org/git/wine.git/blob/56e7cd12ce0ce3bb331a8595b25aedb…
Currently investigating bug 23221 where the application massively leaks GDI
handles. App bug, most likely unrelated to the actual problem of the ticket.
I wanted to see the leakage in a realtime-view with absolute values, leak rate
per second, changes when doing certain UI actions. It's possible to extract
that from Wine trace logs as well using timestamps and filtering for specific
messages but it takes way more effort to associate the leak rate with certain
UI actions (controls).
Multiple tools provide that information in a convenient way. Unfortunately they
rely on the shared handle table being exposed.
---
* https://www.nirsoft.net/utils/gdi_handles.html ("GDIView - View GDI
handles/resources list and detect GDI leaks")
Stable download link via Internet Archive:
https://web.archive.org/web/20201127182337/http://www.nirsoft.net/utils/gdi…
*
https://docs.microsoft.com/en-us/archive/msdn-magazine/2003/january/detect-…
("Detect and Plug GDI Leaks in Your Code with Two Powerful Tools for Windows
XP")
Stable download link via Internet Archive:
https://web.archive.org/web/20170911002438/http://download.microsoft.com/do…
The MSDN article provides the struct layout for entry:
--- quote ---
In his book Windows Graphics Programming: Win32 GDI and DirectDraw (Prentice
Hall, 2002), Feng Huan provides another way to access this table, but he also
describes the structure of each of the 0x4000 entries of this table, as you can
see here:
...
typedef struct {
DWORD pKernelInfo;
WORD ProcessID;
WORD _nCount;
WORD nUpper;
WORD nType;
DWORD pUserInfo;
} GDITableEntry;
--- quote ---
'GDILeaks' self-extractor contains multiple example applications as binaries
and with sources.
https://www.geoffchappell.com/studies/windows/win32/ntdll/structs/peb/index…
--- quote ---
Offset (x86) Offset (x64) Definition Versions
0x94 0xF8 PVOID GdiSharedHandleTable; 3.51 and higher
--- quote ---
The app crashes because the 'PEB->GdiSharedHandleTable' pointer is NULL:
--- snip ---
$ WINEDEBUG=+seh,+relay wine ./GDIView.exe >>log.txt 2>&1
...
0104:Call KERNEL32.GetModuleHandleW(140011eb0 L"ntdll.dll") ret=140004c52
...
0104:Ret KERNEL32.GetModuleHandleW() retval=7bc00000 ret=140004c52
0104:Call KERNEL32.GetProcAddress(7bc00000,140011ec8 "RtlGetCurrentPeb")
ret=140004c67
0104:Ret KERNEL32.GetProcAddress() retval=7bc068e4 ret=140004c67
0104:Call ntdll.RtlGetCurrentPeb() ret=140004c6e
0104:Ret ntdll.RtlGetCurrentPeb() retval=7fffffdaf000 ret=140004c6e
0104:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000140004CA6
ip=0000000140004CA6 tid=0104
0104:trace:seh:dispatch_exception info[0]=0000000000000000
0104:trace:seh:dispatch_exception info[1]=0000000000000008
0104:trace:seh:dispatch_exception rax=0000000000000000 rbx=0000000000f314c0
rcx=000000000021ee48 rdx=0000000000000000
0104:trace:seh:dispatch_exception rsi=0000000000000000 rdi=0000000000000000
rbp=0000000000000000 rsp=000000000021edf8
0104:trace:seh:dispatch_exception r8=000000000021ee30 r9=0000000000000000
r10=0000000000000000 r11=0000000000000246
0104:trace:seh:dispatch_exception r12=0000000000000415 r13=0000000000000001
r14=0000000000000000 r15=000000000021f168
0104:trace:seh:call_vectored_handlers calling handler at 000000007B011BA0
code=c0000005 flags=0
0104:trace:seh:call_vectored_handlers handler at 000000007B011BA0 returned 0
0104:warn:seh:virtual_unwind exception data not found in L"GDIView.exe"
--- snip ---
Wine source:
--- snip ---
$ grep -Hrni GdiSharedHandleTable
include/winternl.h:339: PVOID GdiSharedHandleTable;
/* 094/0f8 */
include/winternl.h:584: ULONG64 GdiSharedHandleTable;
/* 00f8 */
--- snip ---
https://source.winehq.org/git/wine.git/blob/56e7cd12ce0ce3bb331a8595b25aedb…
(x86)
https://source.winehq.org/git/wine.git/blob/56e7cd12ce0ce3bb331a8595b25aedb…
(x86_64)
$ sha1sum gdiview*.zip
4bacc3fed9a41678c72eba41937ff73b7e98ee90 gdiview-x64.zip
1115a41a1784127380ac2df0d3960f4bf09955db gdiview.zip
$ du -sh gdiview*.zip
68K gdiview-x64.zip
52K gdiview.zip
$ wine --version
wine-6.0-rc3
Regards
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53392
Bug ID: 53392
Summary: does not compile on Openindiana (solaris11)
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Solaris
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: malicorne(a)chez.com
It seems that wine does not respect the CFLAGS or at least to some extend.
$ uname -a
SunOS addie 5.11 illumos-c1bbf9203b i86pc i386 i86pc illumos
$ ./configure CFLAGS="-fPIC" CXXFLAGS="-fPIC" --prefix=/opt/wine
$ make
[...]
gcc -o tools/winegcc/winegcc tools/winegcc/utils.o tools/winegcc/winegcc.o
-lsocket -lnsl
tools/winegcc/winegcc -o dlls/acledit/acledit.dll.so --wine-objdir . -fno-PIC
-fasynchronous-unwind-tables -shared \
dlls/acledit/acledit.spec -Wb,--prefer-native -mno-cygwin dlls/acledit/main.o
\
dlls/winecrt0/libwinecrt0.a dlls/ucrtbase/libucrtbase.a
dlls/kernel32/libkernel32.a \
dlls/ntdll/libntdll.a
Text relocation remains referenced
against symbol offset in file
.rodata (section) 0x11010 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11017 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11030 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11037 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11050 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11057 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11070 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11077 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11090 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x11097 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x110b0 acledit.dll-62d91a2e.spec.o
.rodata (section) 0x110b7 acledit.dll-62d91a2e.spec.o
.data (section) 0x110d5 acledit.dll-62d91a2e.spec.o
.data (section) 0x110f1 acledit.dll-62d91a2e.spec.o
.data (section) 0x11102 acledit.dll-62d91a2e.spec.o
.data (section) 0x1110a acledit.dll-62d91a2e.spec.o
.data (section) 0x11112 acledit.dll-62d91a2e.spec.o
.data (section) 0x1111a acledit.dll-62d91a2e.spec.o
.data (section) 0x11122 acledit.dll-62d91a2e.spec.o
ld: fatal: relocations remain against allocatable but non-writable sections
collect2: error: ld returned 1 exit status
winegcc: /usr/bin/gcc failed
make: *** [Makefile:1380: dlls/acledit/acledit.dll.so] Error 2
Error on line 4
If I replace the -fno-PIC by -fPIC as requested on CFLAGS, it does go on until
next time.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=32893
Bug #: 32893
Summary: SNES9x DirectDraw display not refreshed correctly when
menus shown
Product: Wine
Version: 1.5.23
Platform: x86-64
URL: http://files.ipherswipsite.com/snes9x/snes9x-1.53-win3
2.zip
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
Created attachment 43440
--> http://bugs.winehq.org/attachment.cgi?id=43440
Showing refresh problem #1
I'm testing with Wine 1.5.23, SNES9x 1.53, Lubuntu 11.10 x86-64, Nvidia driver
304.64.
There is a small issue with the way the SNES9x DirectDraw display is refreshed.
When you browse the menus, as you move from menu to menu the previous menu area
is cleared to black, instead of showing the emulated game.
There was a change at some point between Wine 1.5.18 and 1.5.23. With 1.5.18
all "old" menus remained onscreen (see
http://bugs.winehq.org/attachment.cgi?id=42660), so the current behaviour is
better but not perfect.
To reproduce
- Download and unzip SNES9x.
- Download a SNES ROM, e.g. from
http://pdroms.de/files/supernintendoentertainmentsystem/skipp-and-friends-p…
- Run SNES9x. Select File->Load Game... and select SAF.smc
- Currently the default Direct3D output gives an empty/black window (bug
32319). So change to DirectDraw output: select Video->Display Configuration...,
change Output Method to DirectDraw and click OK.
- Click on the menu bar to browse the menus. As you move from menu to menu,
notice that the region which was occupied by the previously-shown menu is
black.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44507
Bug ID: 44507
Summary: Railroad Tycoon 3 (GOG version): invisible mouse
cursor in RT3 Mini-Game
Product: Wine
Version: 3.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: t6zm3v62fkp7fe5(a)yandex.ru
Distribution: ---
Created attachment 60464
--> https://bugs.winehq.org/attachment.cgi?id=60464
Screenshot
Railroad Tycoon 3 (GOG version) has additional RT3 Mini-Game. But it's
impossible to play it because the mouse cursor becomes transparent after moving
it into the game's window and appears over after moving it out (but it works,
you can even try to move rails with this invisible cursor until you get tired,
screenshot is attached).
Terminal shows only this:
1@device:~$ WINEARCH=win32 WINEPREFIX=~/win32 wine '/home/1/win32/drive_c/GOG
Games/Railroad Tycoon 3/_Extras/MiniGame/RT3Game.exe'
0009:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
002f:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
Lubuntu 16.04.3, Wine 3.1 from official PPA.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53379
Bug ID: 53379
Summary: ME3Tweaks 7.0.7 doesn't launch
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)tutanota.com
Distribution: ---
ME3Tweaks Mod Manager, the mod manager for the Mass Effect game saga, doesn't
launch on version 7.0.7.125, the latest at the time of writing. All previous
versions launch as expected.
Reproducing the issue is simple: download the program (links below), install
it, and attempt to launch it.
An interesting difference in the logs is in the second line. I don't know if
it's relevant.
On 7.0.6 (the working version), it's:
0310:fixme:seh:WerRegisterRuntimeExceptionModule
(L"C:\\users\\user\\Temp\\.net\\ME3TweaksModManager\\LyZyGpfEln90Fkxp5ZGXmnrlwemKAtA=\\mscordaccore.dll",
0000000180000000) stub
And if you look in that path, mscordaccore.dll is there.
However, in 7.0.7 (the broken version):
010c:fixme:seh:WerRegisterRuntimeExceptionModule
(L"Z:\\home\\user\\ME3-7.0.7\\drive_c\\users\\user\\Documents\\ME3TweaksModManager\\mscordaccore.dll",
0000000140000000) stub
And mscordaccore.dll is not in that path, nor in that Temp folder from before.
Links:
Project repository: https://github.com/ME3Tweaks/ME3TweaksModManager
Latest version, the broken one:
https://github.com/ME3Tweaks/ME3TweaksModManager/releases/download/7.0.7.12…
Last working version:
https://github.com/ME3Tweaks/ME3TweaksModManager/releases/download/7.0.6.12…
Changes between versions:
https://github.com/ME3Tweaks/ME3TweaksModManager/compare/7.0.6.124...7.0.7.…
Linux 5.18.12-zen1, NixOS unstable 22.11.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51682
Bug ID: 51682
Summary: LINE detects Wine as Win7/Win8 even with winecfg set
to Win10
Product: Wine
Version: 6.15
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Reported in the forums under https://forum.winehq.org/viewtopic.php?f=8&t=35589
The program installs fine, but when running it complains that it can't run
under Win7/Win8. Setting Win10 in winecfg doesn't help.
https://desktop.line-scdn.net/win/new/LineInst.exe
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50839
Bug ID: 50839
Summary: DARQ has no shadows with OpenGL renderer
Product: Wine
Version: 6.4
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 69655
--> https://bugs.winehq.org/attachment.cgi?id=69655
example
0408:err:d3d:wined3d_debug_callback 0x24d585b0:
"GL_INVALID_FRAMEBUFFER_OPERATION in glDrawElements(incomplete framebuffer)".
0408:fixme:d3d:wined3d_context_gl_check_fbo_status FBO status
GL_FRAMEBUFFER_INCOMPLETE_LAYER_TARGETS (0x8da8).
0408:fixme:d3d:context_dump_fbo_attachment GL_DEPTH_ATTACHMENT: 2d texture
282, 256x256, 0 samples, format 0x81a5.
0408:fixme:d3d:context_dump_fbo_attachment GL_STENCIL_ATTACHMENT: NONE.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT0: 2d-array
texture 275, 256x256, 0 samples, format 0x822e.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT1: NONE.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT2: NONE.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT3: NONE.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT4: NONE.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT5: NONE.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT6: NONE.
0408:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT7: NONE.
wine-6.4-180-g41df83c50e1
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48306
Bug ID: 48306
Summary: Roblox Player: Client kicked with Error Code 268
Product: Wine
Version: 5.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nerdyminer18(a)gmail.com
Distribution: ---
To preface this, Wine cannot normally run the Roblox Player unless a tool, like
Grapejuice (https://gitlab.com/brinkervii/grapejuice), is installed so Wine can
launch the application from the Roblox website.
Whenever the Roblox Player connects to a game, there is a ~5 second window
where the application will work properly until the client is forced to
disconnect by the server. When this happens, a box with the text "Disconnected
| You have been kicked due to unexpected client behavior (Error Code: 268)"
appears. This error code only appears when the application detects that an
external application is modifying the application(Ex: Running Cheat Engine's
debugger triggers this error). Wine in this case is being treated as a sort of
exploit in the case that it's trying to modify the application somehow.
[I cannot provide a log/backtrace as of the time this bug gets submitted, but I
will do so later on]
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39390
Bug ID: 39390
Summary: Backgrounds are black in 99 Spirits
Product: Wine
Version: 1.7.51
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: funtimeschaos(a)rocketmail.com
Distribution: ---
Created attachment 52501
--> https://bugs.winehq.org/attachment.cgi?id=52501
Terminal output
All backgrounds fail to render, replaced by plain blackness instead.
The terminal doesn't seem to provide much helpful out, but I've attached it
regardless.
According to the terminal, this may be a duplicate of 9127, but the normal work
around steps (winetricks quartz, wmp10, allcodecs) removed the quartz fixme
messages but not the problem.
Would love to put up a more helpful output, if I knew which WINEDEBUG flags to
use.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.