November 2023 - Wine-bugs - list.winehq.org

[Bug 55662] New: Different behaviour of "set" command
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55662 Bug ID: 55662 Summary: Different behaviour of "set" command Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: ch.panel(a)free.fr Distribution: --- behavior of these commands are different in wine and windows in a batch file set test=A set /P test="type A or B (%test%) :" echo "%test%" pause if the user type nothing the result is : "A" on windows "" on wine -- 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.

1 5

[Bug 55798] New: Unreal Engine 5.2: Wine minidumps take hours to load into a debugger
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55798 Bug ID: 55798 Summary: Unreal Engine 5.2: Wine minidumps take hours to load into a debugger Product: Wine Version: 8.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: aiden.deloryn(a)tensorworks.com.au Distribution: --- === Overview === When attempting to load a Wine generated minidump from an Unreal Engine application using a debugger (such as Visual Studio or VS Code), it takes a number of hours for the file to load. If left uninterrupted during this time, the process does eventually complete and all of the expected debug data becomes visible within the IDE. This behaviour has only been observed for minidumps of type MiniDumpNormal. When working with a Wine generated minidump of type MiniDumpWithFullMemory, the debugger is able to load the file within a few seconds. === Steps to Reproduce === 1. Build this minimal sample application https://github.com/TensorWorks/BuggyFirstPersonDemo.git on a Windows machine with Unreal Engine 5.2.1 using the following command: C:\<UE_INSTALL_DIR>\Engine\Build\BatchFiles\RunUAT.bat BuildCookRun -utf8output -clientconfig=DebugGame -project="C:\<PATH_TO_PROJECT_DIR>\BuggyFirstPersonDemo.uproject" -noP4 -cook -build -stage -prereqs -pak -archive -archivedirectory="C:\<PATH_TO_PROJECT_DIR>\GameBuilds" -platform=Win64 2. Copy the build directory (C:\<PATH_TO_PROJECT_DIR>\GameBuilds) to a Linux machine and run the application using Wine (DXVK required): wine ./GameBuilds/Windows/BuggyFirstPersonDemo/Binaries/Win64/BuggyFirstPersonDemo-Win64-DebugGame.exe -windowed -ResX=800 -ResY=600 3. Trigger a crash by picking up the gun and shooting the large white cube. Note: hold down the right mouse button to aim/look, and press the left mouse button to shoot. 4. Copy the crash dump from ./GameBuilds/Windows/BuggyFirstPersonDemo/Saved/Crashes/<CRASH_ID>/UEMinidump.dmp to a Windows machine and attempt to load it using Visual Studio or VS Code (for VS Code you will need the C/C++ extension from Microsoft installed). === Actual Results === The minidump takes hours to load into Visual Studio and VS Code. MemoryListStream contains over 950,000 memory ranges (see additional information below). === Expected Results === The minidump takes less than a minute to load into Visual Studio and VS Code, which is true for full memory minidumps generated under Wine and any minidump generated under Windows. === Build Date & Hardware === wine-8.14 on Ubuntu 22.04.3 LTS x86-64 === Additional Builds and Platforms === Also reproducible on wine-8.17 and wine-8.0.2 === Additional Information === When analysing and comparing minidumps generated under Wine versus those generated under Windows using the Microsoft Crash Dump File Checker tool “DumpChk” (https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/dumpchk) a significant discrepancy can be observed in the normal minidump generated under Wine. In particular, the number of memory ranges in MemoryListStream is substantially higher, as can be seen in the excerpts below. Note that full memory minidumps have also been included from both Windows and Wine for additional context and comparison. Windows - MiniDumpNormal: Stream 3: type MemoryListStream (5), size 00000804, RVA 0006FF09 128 memory ranges [OMITTED] Total memory: 463cc Wine - MiniDumpNormal: Stream 4: type MemoryListStream (5), size 00EA0FF4, RVA 0002986B 958719 memory ranges [OMITTED] Total memory: 15bd62e Windows - MiniDumpWithFullMemory: Stream 5: type Memory64ListStream (9), size 0000EAC0, RVA 000C8D45 3755 memory ranges [OMITTED] Total memory: a74c1000 Wine - MiniDumpWithFullMemory: Stream 7: type Memory64ListStream (9), size 0000E260, RVA 0006ADFB 3621 memory ranges [OMITTED] Total memory: 7ab14000 Note: You can generate a full memory minidump using the provided sample application by specifying the -fullcrashdumpalways flag. For example: wine ./GameBuilds/Windows/BuggyFirstPersonDemo/Binaries/Win64/BuggyFirstPersonDemo-Win64-DebugGame.exe -windowed -ResX=800 -ResY=600 -fullcrashdumpalways -- 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.

1 3

[Bug 48455] New: Native Instruments Native Access 1.9 installer hangs during installation of ISO Mounter driver (missing handling of architecture-specific SourceDisks{Names,Files} .inf sections)
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=48455 Bug ID: 48455 Summary: Native Instruments Native Access 1.9 installer hangs during installation of ISO Mounter driver (missing handling of architecture-specific SourceDisks{Names,Files} .inf sections) Product: Wine Version: 5.0-rc5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. The driver sub-installer just hangs (churning cpu), blocking the main installer forever. Stable download link via Internet Archive: https://web.archive.org/web/20190227215247/https://www.native-instruments.c… --- snip --- $ wine ./Native\ Access\ 1.9.1\ Setup\ PC.exe ... --- snip --- Reduced case by calling driver sub-installer directly, after killing main installer: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files (x86)/Native Instruments/IsoDriver/x64 $ WINEDEBUG=+seh,+relay,+loaddll,+process,+setupapi wine ./NI-drvinst.exe instroot "root\NIWinCDEmu" "C:\Program Files (x86)\Native Instruments\IsoDriver\NIWinCDEmu.inf" >>log.txt 2>&1 ... 002d:trace:setupapi:SetupDiInstallDriverFiles devinfo 000000000011C1C0, device_data 000000000022F6C0. ... 002d:trace:setupapi:SetupOpenInfFileW L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.inf" -> 000000000011D990 ... 002d:trace:setupapi:SetupGetStringFieldW context 000000000011D990/000000000011D990/9/0 index 1 returning L"Drivers_Dir" ... 002d:trace:setupapi:SetupQueueCopySectionW queue 000000000011DDD0, src_root L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver", hinf 000000000011D990, hlist 000000000011D990, section L"Drivers_Dir", style 0x10000. ... 002d:trace:setupapi:SetupQueueCopyIndirectW root=L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver" path=(null) file=L"NIWinCDEmu.sys" -> dir=L"C:\\windows\\system32\\drivers" file=L"NIWinCDEmu.sys" descr=(null) tag=(null) ... 002d:trace:setupapi:SetupDefaultQueueCallbackW start copy L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" -> L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" ... 002d:trace:setupapi:queue_copy_file copying file L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" -> L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" ... 002d:trace:setupapi:do_file_copyW copy L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" to L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" style 0x10000 002d:Call KERNEL32.GetFileAttributesW(006fd540 L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys") ret=00259e09 ... 002d:Ret KERNEL32.GetFileAttributesW() retval=ffffffff ret=00259e09 002d:Call KERNEL32.CopyFileW(006fd4a0 L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys",006fd540 L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys",00000000) ret=0025a064 .... 002d:Call ntdll.NtCreateFile(0022e100,80100080,0022e128,0022e118,00000000,00000000,00000007,00000001,00000060,00000000,00000000) ret=7b0110a1 002d:Ret ntdll.NtCreateFile() retval=c0000034 ret=7b0110a1 002d:Call ntdll.RtlNtStatusToDosError(c0000034) ret=7b011190 002d:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=7b011190 ... 002d:Ret KERNEL32.CopyFileW() retval=00000000 ret=0025a064 002d:warn:setupapi:do_file_copyW failed to copy, err 2 ... <repeats endlessly> ... 002d:trace:setupapi:SetupDefaultQueueCallbackW need media L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver" L"NIWinCDEmu.sys" ... 002d:trace:setupapi:SetupDefaultQueueCallbackW start copy L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" -> L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" ... --- snip --- Content of 'NIWinCDEmu.inf': --- snip --- [Version] Signature="$WINDOWS NT$" Class=SCSIAdapter ClassGuid={4d36e97b-e325-11ce-bfc1-08002be10318} Provider=%NI_MFNAME% DriverVer= 08/05/2011, 1.0.0.2 CatalogFile=NIWinCDEmu.cat [DestinationDirs] DefaultDestDir = 12 [SourceDisksNames.x86] 1 = %DiskId1%,,, [SourceDisksNames.amd64] 1 = %DiskId1%,,, [SourceDisksFiles.x86] NIWinCDEmu.sys = 1,\x86 [SourceDisksFiles.amd64] NIWinCDEmu.sys = 1,\x64 [Manufacturer] %NI_MFNAME%=Standard, NTamd64 [Standard] %NIWinCDEmu.DeviceDesc%=NIWinCDEmu_Device, root\NIWinCDEmu [Standard.NTamd64] %NIWinCDEmu.DeviceDesc%=NIWinCDEmu_Device, root\NIWinCDEmu [NIWinCDEmu_Device.NT] CopyFiles=Drivers_Dir [Drivers_Dir] NIWinCDEmu.sys,,,2 ;-------------- Service installation [NIWinCDEmu_Device.NT.Services] AddService = NIWinCDEmu,%SPSVCINST_ASSOCSERVICE%, dev_Service_Inst ; -------------- busenum driver install sections [dev_Service_Inst] DisplayName = %dev.SVCDESC% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\NIWinCDEmu.sys LoadOrderGroup = Extended Base [Strings] SPSVCINST_ASSOCSERVICE= 0x00000002 NI_MFNAME = "Native Instruments GmbH" DiskId1 = "ISO Mounter Installation Disk #1" NIWinCDEmu.DeviceDesc = "ISO Mounter" dev.SVCDESC = "ISO Mounter driver" --- snip --- The problem here is that Wine's 'get_source_info' doesn't take architecture-specific 'SourceDisksNames' and 'SourceDisksFiles' .inf sections into account. Wine source: https://source.winehq.org/git/wine.git/blob/b3abc343c373ee5fd0764a3ceedeef5… --- snip --- 289 static void get_source_info( HINF hinf, const WCHAR *src_file, SP_FILE_COPY_PARAMS_W *params, 290 WCHAR *src_root, WCHAR *src_path) 291 { 292 static const WCHAR SourceDisksNames[] = 293 {'S','o','u','r','c','e','D','i','s','k','s','N','a','m','e','s',0}; 294 static const WCHAR SourceDisksFiles[] = 295 {'S','o','u','r','c','e','D','i','s','k','s','F','i','l','e','s',0}; 296 297 INFCONTEXT file_ctx, disk_ctx; 298 INT id, diskid; 299 DWORD len; 300 301 /* find the SourceDisksFiles entry */ 302 if (!SetupFindFirstLineW( hinf, SourceDisksFiles, src_file, &file_ctx )) return; 303 if (!SetupGetIntField( &file_ctx, 1, &diskid )) return; 304 305 /* now find the diskid in the SourceDisksNames section */ 306 if (!SetupFindFirstLineW( hinf, SourceDisksNames, NULL, &disk_ctx )) return; 307 for (;;) 308 { 309 if (SetupGetIntField( &disk_ctx, 0, &id ) && (id == diskid)) break; 310 if (!SetupFindNextLine( &disk_ctx, &disk_ctx )) return; 311 } 312 313 if (SetupGetStringFieldW( &disk_ctx, 1, NULL, 0, &len ) && len > sizeof(WCHAR) 314 && (params->SourceDescription = heap_alloc( len * sizeof(WCHAR) ))) 315 SetupGetStringFieldW( &disk_ctx, 1, (WCHAR *)params->SourceDescription, len, NULL ); 316 317 if (SetupGetStringFieldW( &disk_ctx, 2, NULL, 0, &len ) && len > sizeof(WCHAR) 318 && (params->SourceTagfile = heap_alloc( len * sizeof(WCHAR) ))) 319 SetupGetStringFieldW( &disk_ctx, 2, (WCHAR *)params->SourceTagfile, len, NULL ); 320 321 if (SetupGetStringFieldW( &disk_ctx, 4, NULL, 0, &len ) && len > sizeof(WCHAR) 322 && len < MAX_PATH - lstrlenW( src_root ) - 1) 323 { 324 lstrcatW( src_root, backslashW ); 325 SetupGetStringFieldW( &disk_ctx, 4, src_root + lstrlenW( src_root ), 326 MAX_PATH - lstrlenW( src_root ), NULL ); 327 } 328 329 if (SetupGetStringFieldW( &file_ctx, 2, NULL, 0, &len ) && len > sizeof(WCHAR) && len < MAX_PATH) 330 { 331 SetupGetStringFieldW( &file_ctx, 2, src_path, MAX_PATH, NULL ); 332 params->SourcePath = src_path; 333 } 334 } --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-sourc… --- quote ---- ... To support distribution of driver files on multiple system architectures, you can specify an architecture-specific SourceDisksFiles section by adding an .x86, .ia64, .amd64, .arm, or .arm64 extension to SourceDisksFiles. Be aware that, unlike other sections such as a DDInstall section, the platform extensions for a SourceDisksFiles section are not .ntx86, .ntia64, or .ntamd64. For example, to specify a source disk names section for an x86-based system, use a SourceDisksFiles.x86 section, not a SourceDisksFiles.ntx86 section. Similarly, use a SourceDisksFiles.ia64 section to specify an Itanium-based system and a SourceDisksFiles.amd64 section to specify an x64-based system. During installation, SetupAPI functions look for architecture-specific SourceDisksFiles sections before using the generic section. For example, if, during installation on an x86-based platform, Windows is copying a file that is named driver.sys, it will look for the file's description in [SourceDisksFiles.x86] before looking in [SourceDisksFiles]. --- quote ---- In contrast, 'get_source_id' does it properly: https://source.winehq.org/git/wine.git/blob/f1b94dc16c35a5c477b6df8aa94c6d3… --- snip --- 372 static LPWSTR get_source_id( HINF hinf, PINFCONTEXT context, PCWSTR filename ) 373 { 374 DWORD size; 375 LPWSTR source_id; 376 377 if (!SetupFindFirstLineW( hinf, source_disks_files_platform, filename, context ) && 378 !SetupFindFirstLineW( hinf, source_disks_files, filename, context )) 379 return NULL; 380 381 if (!SetupGetStringFieldW( context, 1, NULL, 0, &size )) 382 return NULL; 383 384 if (!(source_id = HeapAlloc( GetProcessHeap(), 0, size * sizeof(WCHAR) ))) 385 return NULL; 386 387 if (!SetupGetStringFieldW( context, 1, source_id, size, NULL )) 388 { 389 HeapFree( GetProcessHeap(), 0, source_id ); 390 return NULL; 391 } 392 393 if (!SetupFindFirstLineW( hinf, source_disks_names_platform, source_id, context ) && 394 !SetupFindFirstLineW( hinf, source_disks_names, source_id, context )) 395 { 396 HeapFree( GetProcessHeap(), 0, source_id ); 397 return NULL; 398 } 399 return source_id; 400 } --- snip --- $ sha1sum Native* 374f62fb373ceb02527b8a179c7e305268bab25c Native Access 1.9.1 Setup PC.exe 5a78d5850267d0ef6701bc5da7dc25e5b62b6031 Native_Access_Installer.zip $ du -sh Native* 70M Native Access 1.9.1 Setup PC.exe 69M Native_Access_Installer.zip $ wine --version wine-5.0-rc5 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.

1 12

[Bug 48525] New: 0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
by WineHQ Bugzilla 26 Jul '24

26 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=48525 Bug ID: 48525 Summary: 0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: cagnulein(a)gmail.com Distribution: --- On a commercial application written on .NET 2.0 i have a crash that occurs randomly every few days. I put the +seh debug here. I have 2 questions: 1) my +seh log file is full of 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0048 0048:trace:seh:raise_exception info[0]=00000041 0048:trace:seh:raise_exception info[1]=0d061dd8 0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef20 edx=0733efd0 esi=00000041 edi=40010006 0048:trace:seh:raise_exception ebp=0733ef78 esp=0733eef4 cs=300023 ds=002b es=f7d7002b fs=006b gs=73c0063 flags=00000212 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c edx=0733efd8 esi=0733efd8 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 it's a problem of my application? Of wine gdiplus implementation? 2) In the meanwhile i'm trying with "winetricks gdiplus": what you think about this +seh trace? 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c edx=0733efd8 esi=0733efd8 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0048 0048:trace:seh:raise_exception info[0]=00000041 0048:trace:seh:raise_exception info[1]=0d061dd8 0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef20 edx=0733efd0 esi=00000041 edi=40010006 0048:trace:seh:raise_exception ebp=0733ef78 esp=0733eef4 cs=300023 ds=002b es=f7d7002b fs=006b gs=73c0063 flags=00000212 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef0c edx=0733efd8 esi=0733efd8 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eac8 esp=0733eaa8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0048:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0048 0048:trace:seh:raise_exception info[0]=0000003e 0048:trace:seh:raise_exception info[1]=0d0719e8 0048:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0733ef50 edx=0733f000 esi=0000003e edi=40010006 0048:trace:seh:raise_exception ebp=0733efa8 esp=0733ef24 cs=0023 ds=34002b es=733002b fs=7dd9006b gs=7330063 flags=00000216 0048:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0048:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0733ef3c edx=0733f008 esi=0733f008 edi=7b48ace0 0048:trace:seh:__regs_RtlUnwind ebp=0733eaf8 esp=0733ead8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0048:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0048:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0009:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43e223 ip=7b43e223 tid=0009 0009:trace:seh:raise_exception info[0]=00000046 0009:trace:seh:raise_exception info[1]=0d068440 0009:trace:seh:raise_exception eax=7b42a5c1 ebx=00000004 ecx=0032e720 edx=0032e7d0 esi=00000046 edi=40010006 0009:trace:seh:raise_exception ebp=0032e778 esp=0032e6f4 cs=0023 ds=34002b es=002b fs=006b gs=0063 flags=00000212 0009:trace:seh:call_stack_handlers calling handler at 0x7b48ad80 code=40010006 flags=0 0009:trace:seh:__regs_RtlUnwind code=40010006 flags=2 0009:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7b48ace0 ecx=0032e70c edx=0032e7d8 esi=0032e7d8 edi=7b48ace0 0009:trace:seh:__regs_RtlUnwind ebp=0032e2c8 esp=0032e2a8 eip=7b48ad3d cs=0023 ds=002b fs=006b gs=0063 flags=00000202 0009:trace:seh:__regs_RtlUnwind calling handler at 0x7bc82da0 code=40010006 flags=2 0009:trace:seh:__regs_RtlUnwind handler at 0x7bc82da0 returned 1 0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash Fatal,Program[1:MainThread]: System.Runtime.InteropServices.SEHException: External component has thrown an exception. at System.Drawing.SafeNativeMethods.SelectObject(HandleRef hdc, HandleRef obj) at System.Drawing.BufferedGraphicsContext.DisposeDC() at System.Drawing.BufferedGraphicsContext.ReleaseBuffer(BufferedGraphics buffer) at System.Drawing.BufferedGraphics.Dispose(Boolean disposing) at System.Drawing.BufferedGraphics.Dispose() at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Label.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) I can't share the application because it's not free, but if you need more information i will try to get them. Thanks in advance -- 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.

1 6

[Bug 55818] New: 32-bit game Dark Age of Camelot slow memory leak leads to crash since WINE 7.4
by WineHQ Bugzilla 25 Jul '24

25 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55818 Bug ID: 55818 Summary: 32-bit game Dark Age of Camelot slow memory leak leads to crash since WINE 7.4 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: tmwine(a)pertho.net Distribution: --- I've bisected a bug relating to a possible memory leak in wined3d. I've been playing an old game (Dark Age of Camelot) for years now on free servers, but I noticed there is a slow memory leak as it runs. I ran 'top' and watched the RES memory creep up to 1.0 GB and then hit about 1.2-1.3 GB before the game crashes. On WINE 8 this issue seems to persist as well. So I went back and bisected the bug and it occurs between WINE 7.3 and 7.4. In 7.3, I don't get the memory leak and the game plays for hours, but in 7.4 I get the memory leak. I've narrowed it down to this commit: https://gitlab.winehq.org/wine/wine/-/commit/ee12556960e30fc22f276d2de2833e… It might have to do with the code change in the function wined3d_context_gl_destroy_bo that introduced this. Happy to try any patches to test with against latest WINE 8.x tree. Thanks, Tom -- 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.

1 43

[Bug 44962] New: Smart Guard no run
by wine-bugs＠winehq.org 23 Jul '24

23 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=44962 Bug ID: 44962 Summary: Smart Guard no run Product: Wine-staging Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: terapy-session(a)bk.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 61074 --> https://bugs.winehq.org/attachment.cgi?id=61074 averia petch, l2.exe log Smart Guard does not work and cannot work around it. Checked on different servers, but I give a log from the server Averia.ws -- 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.

2 18

[Bug 48372] New: SCP-3008 Unhandled exception: page fault on read access to
by WineHQ Bugzilla 22 Jul '24

22 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=48372 Bug ID: 48372 Summary: SCP-3008 Unhandled exception: page fault on read access to Product: Wine Version: 4.0.3 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zach.stuart(a)ztex.us Created attachment 66123 --> https://bugs.winehq.org/attachment.cgi?id=66123 crash debug output Game begins to load and then fails before fully loading. -- 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.

1 3

[Bug 37296] New: Winecfg differs when it runs on real Windows
by wine-bugs＠winehq.org 21 Jul '24

21 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=37296 Bug ID: 37296 Summary: Winecfg differs when it runs on real Windows Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: carlo.bramix(a)libero.it Created attachment 49603 --> https://bugs.winehq.org/attachment.cgi?id=49603 Screenshot of Winecfg on Windows I'm able to run Winecfg on real Windows and I discovered that there is a graphic glitch in the about dialog. See attached screenshot for details. I was able to fix this problem in about.c, by adding DI_MASK flag in the call of DrawIconEx(), which it is also the correct thing to do in this case. But strangely, this graphic bug does not happen when winecfg runs in WINE (that's why probably nobody noticed the absence of the DI_MASK flag). I would suggest to check and compare a bit the behaviour between Windows and WINE against the functions DrawIconEx() and LoadImageW() since it seems to me that there is a difference from the correct result. NOTE: When it runs on the real Windows, because the presence of a SysLink inside the resource dialog, Winecfg requires to be linked with commctrl v6, so it needs a manifest file, as explained here: http://msdn.microsoft.com/en-us/library/windows/desktop/bb773175%28v=vs.85%… Another thing, but less important, is that the resource compiler refused the icon of the application, saying the icon is made with the old DIB format and, for this reason, it has been discarded; that's why my screenshot shows the app without the icon in the upper left corner. But hopefully, this can be solved easily if someone wants. -- 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.

2 9

[Bug 55512] New: error in movie maker 2012 in 32-bit mode
by WineHQ Bugzilla 21 Jul '24

21 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55512 Bug ID: 55512 Summary: error in movie maker 2012 in 32-bit mode Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: grandrodri3(a)gmail.com Distribution: --- Created attachment 75076 --> https://bugs.winehq.org/attachment.cgi?id=75076 error that I get when running the movie maker with the stable version of wine Hello, I have been testing the movie maker, the latest one, I have read some instructions that are on the internet and I have tried it, I have put the report in the corresponding section, what yes, I have tried the movie maker in 32-bit mode and it gives me error, could you review it?, thanks I attached the error report that gives All the best PS: tested libraries net framework d3dx9 and 10 ie8 media player -- 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.

1 7

[Bug 49420] New: Ableton 10: file dialogs not DPI scaled
by WineHQ Bugzilla 20 Jul '24

20 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=49420 Bug ID: 49420 Summary: Ableton 10: file dialogs not DPI scaled Product: Wine Version: 5.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: io(a)mikelpr.com Distribution: --- the file open/save dialogs are not scaled when running with a different DPI, yet the mouse input is - like if the window were actually scaled. therefore, I can only click the top left halves (width and height) of the file dialogs -- 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.

1 2