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

[Bug 36348] New: valgrind shows a couple leaks in d3d9/tests/d3d9ex.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36348 Bug ID: 36348 Summary: valgrind shows a couple leaks in d3d9/tests/d3d9ex.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==3976== 16 bytes in 1 blocks are definitely lost in loss record 396 of 1,973 ==3976== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==3976== by 0x4F58C13: Direct3DCreate9Ex (d3d9_main.c:63) ==3976== by 0x4A557EB: create_device.constprop.1 (d3d9ex.c:59) ==3976== by 0x4A55992: test_reset (d3d9ex.c:684) ==3976== by 0x4A5A5CB: func_d3d9ex (d3d9ex.c:1218) ==3976== by 0x4ADCD4C: run_test (test.h:584) ==3976== by 0x4ADD13B: main (test.h:654) ==3976== ==3976== 12,068 bytes in 1 blocks are definitely lost in loss record 1,915 of 1,973 ==3976== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==3976== by 0x506F901: wined3d_create (wined3d_main.c:95) ==3976== by 0x4F654AE: d3d9_init (directx.c:647) ==3976== by 0x4F58C30: Direct3DCreate9Ex (d3d9_main.c:66) ==3976== by 0x4A557EB: create_device.constprop.1 (d3d9ex.c:59) ==3976== by 0x4A55992: test_reset (d3d9ex.c:684) ==3976== by 0x4A5A5CB: func_d3d9ex (d3d9ex.c:1218) ==3976== by 0x4ADCD4C: run_test (test.h:584) ==3976== by 0x4ADD13B: main (test.h:654) ==3976== -- 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 9

[Bug 36340] New: valgrind shows several warnings in ddraw/tests/ddraw2.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36340 Bug ID: 36340 Summary: valgrind shows several warnings in ddraw/tests/ddraw2.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==20452== Conditional jump or move depends on uninitialised value(s) ==20452== at 0x5842378: GetRegionData (region.c:889) ==20452== by 0x4E726BE: ddraw_clipper_GetClipList (clipper.c:213) ==20452== by 0x4EA05EE: ddraw_surface7_Blt (surface.c:1429) ==20452== by 0x4EA1FE6: ddraw_surface1_Blt (surface.c:1597) ==20452== by 0x4D9776E: test_clipper_blt (ddraw2.c:647) ==20452== by 0x4DA7C8E: func_ddraw2 (ddraw2.c:6398) ==20452== by 0x4E1C6DC: run_test (test.h:584) ==20452== by 0x4E1CACB: main (test.h:654) ==20452== Uninitialised value was created by a stack allocation ==20452== at 0x4EA0411: ddraw_surface7_Blt (surface.c:1503) ==20452== and several leaks, e.g.,: ==20664== 20 bytes in 1 blocks are definitely lost in loss record 208 of 1,043 ==20664== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==20664== by 0x4E8EA7E: DirectDrawCreateClipper (ddraw.c:3274) ==20664== by 0x4E8EC42: ddraw7_CreateClipper (ddraw.c:3309) ==20664== by 0x4E8ED9F: ddraw2_CreateClipper (ddraw.c:3331) ==20664== by 0x4DA6CBC: test_clipper_blt (ddraw2.c:565) ==20664== by 0x4DB7C8E: func_ddraw2 (ddraw2.c:6398) ==20664== by 0x4E2C6DC: run_test (test.h:584) ==20664== by 0x4E2CACB: main (test.h:654) ==20664== -- 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 36621] New: valgrind shows several definite leaks in ddraw/tests/ddraw1.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36621 Bug ID: 36621 Summary: valgrind shows several definite leaks in ddraw/tests/ddraw1.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==13886== 20 bytes in 1 blocks are definitely lost in loss record 205 of 1,033 ==13886== at 0x7BC4C75D: notify_alloc (heap.c:255) ==13886== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==13886== by 0x4B90A4B: DirectDrawCreateClipper (ddraw.c:3274) ==13886== by 0x4B90C0D: ddraw7_CreateClipper (ddraw.c:3309) ==13886== by 0x4B90E50: ddraw1_CreateClipper (ddraw.c:3342) ==13886== by 0x4A6BA13: create_device (ddraw1.c:286) ==13886== by 0x4A6E659: test_coop_level_d3d_state (ddraw1.c:788) ==13886== by 0x4A87307: func_ddraw1 (ddraw1.c:5488) ==13886== by 0x4B24F84: run_test (test.h:584) ==13886== by 0x4B25373: main (test.h:654) ==13886== ==13886== 20 bytes in 1 blocks are definitely lost in loss record 206 of 1,033 ==13886== at 0x7BC4C75D: notify_alloc (heap.c:255) ==13886== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==13886== by 0x4B90A4B: DirectDrawCreateClipper (ddraw.c:3274) ==13886== by 0x4B90C0D: ddraw7_CreateClipper (ddraw.c:3309) ==13886== by 0x4B90E50: ddraw1_CreateClipper (ddraw.c:3342) ==13886== by 0x4A6BA13: create_device (ddraw1.c:286) ==13886== by 0x4A6ED15: test_surface_interface_mismatch (ddraw1.c:860) ==13886== by 0x4A8730C: func_ddraw1 (ddraw1.c:5489) ==13886== by 0x4B24F84: run_test (test.h:584) ==13886== by 0x4B25373: main (test.h:654) ==13886== etc. and one case of: ==13516== 4,096 bytes in 1 blocks are definitely lost in loss record 1,473 of 1,516 ==13516== at 0x72E66F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==13516== by 0x72E2378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0) ==13516== by 0x6EF6DC2: ??? (in /usr/lib/dri/i965_dri.so) ==13516== by 0x6EF8594: ??? (in /usr/lib/dri/i965_dri.so) ==13516== by 0x6EFECCD: ??? (in /usr/lib/dri/i965_dri.so) ==13516== by 0x6D2D411: ??? (in /usr/lib/dri/i965_dri.so) ==13516== by 0x6F0189E: ??? (in /usr/lib/dri/i965_dri.so) ==13516== by 0x6D16339: ??? (in /usr/lib/dri/i965_dri.so) ==13516== by 0x6D1A9E9: ??? (in /usr/lib/dri/i965_dri.so) ==13516== by 0x68D1C95: glTexSubImage2D (in /usr/lib/libGL.so.1.2.0) ==13516== by 0x510FE80: surface_upload_data (surface.c:1641) ==13516== by 0x511D054: surface_load_texture (surface.c:4861) ==13516== by 0x511D52E: surface_load_location (surface.c:4954) ==13516== by 0x5111C25: surface_load (surface.c:2150) ==13516== by 0x51294DA: texture2d_sub_resource_load (texture.c:730) ==13516== by 0x5128AE8: wined3d_texture_load (texture.c:539) ==13516== by 0x50558C7: arbfp_blit_surface (arb_program_shader.c:7653) ==13516== by 0x5121910: wined3d_surface_blt (surface.c:6060) ==13516== by 0x4A9646C: ddraw_surface_blt_clipped (surface.c:1387) ==13516== by 0x4A96CCA: ddraw_surface7_Blt (surface.c:1543) ==13516== -- 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 4

[Bug 36660] New: ddraw/tests/d3d.c CapsTest crashes under valgrind
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36660 Bug ID: 36660 Summary: ddraw/tests/d3d.c CapsTest crashes under valgrind Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 36658, 36659 Created attachment 48699 --> https://bugs.winehq.org/attachment.cgi?id=48699 backtrace =>0 0x06626b00 (0x0525f2c8) 1 0x05347ae5 fixup_extensions+0x57(gl_info=0x4b8cc64, gl_renderer="GeForce GTX 460/PCIe/SSE2", gl_vendor=GL_VENDOR_NVIDIA, card_vendor=HW_VENDOR_NVIDIA, device=CARD_NVIDIA_GEFORCE_GTX460) [/home/austin/wine-valgrind/dlls/wined3d/directx.c:1542] in wined3d (0x0525f308) 2 0x0534df87 wined3d_adapter_init_gl_caps+0x166d(adapter=0x4b8cc54) [/home/austin/wine-valgrind/dlls/wined3d/directx.c:3131] in wined3d (0x0525f4e8) 3 0x0535345a wined3d_adapter_init+0x372(adapter=0x4b8cc54, ordinal=0) [/home/austin/wine-valgrind/dlls/wined3d/directx.c:5180] in wined3d (0x0525f8f8) 4 0x053539b3 wined3d_init+0xb3(wined3d=0x4b8cc48, flags=0x5) [/home/austin/wine-valgrind/dlls/wined3d/directx.c:5272] in wined3d (0x0525f928) 5 0x053fc954 wined3d_create+0xc3(flags=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/wined3d/wined3d_main.c:105] in wined3d (0x0525f998) 6 0x05282e2c ddraw_init+0xa5(ddraw=0x4b8cb98, device_type=0) [/home/austin/wine-valgrind/dlls/ddraw/ddraw.c:4874] in ddraw (0x0525fb78) 7 0x052971f3 DDRAW_Create+0x15f(guid=(nil), DD=0x525fc70, UnkOuter=(nil), iid=0x52c3714) [/home/austin/wine-valgrind/dlls/ddraw/main.c:274] in ddraw (0x0525fbe8) 8 0x05297404 DirectDrawCreate+0xac(driver_guid=<couldn't compute location>, ddraw=<couldn't compute location>, outer=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/ddraw/main.c:309] in ddraw (0x0525fc38) 9 0x04f6b529 CapsTest+0x198() [/home/austin/wine-valgrind/dlls/ddraw/tests/d3d.c:810] in ddraw_test (0x0525fc88) OpenGL renderer string: GeForce GTX 460/PCIe/SSE2 OpenGL core profile version string: 4.3.0 NVIDIA 337.25 -- 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 36201] New: valgrind shows a definite leak under crypt32/tests/store.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36201 Bug ID: 36201 Summary: valgrind shows a definite leak under crypt32/tests/store.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48322 --> https://bugs.winehq.org/attachment.cgi?id=48322 valgrind log ==18714== 48 bytes in 1 blocks are definitely lost in loss record 215 of 443 ==18714== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==18714== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==18714== by 0x514398B: CryptMemAlloc (main.c:124) ==18714== by 0x511E5A6: Context_CreateLinkContext (context.c:60) ==18714== by 0x510AB00: Cert_clone (cert.c:127) ==18714== by 0x511D199: CRYPT_CollectionCreateContextFromChild (collectionstore.c:85) ==18714== by 0x511D5C9: Collection_addCert (collectionstore.c:215) ==18714== by 0x510B119: add_cert_to_store (cert.c:263) ==18714== by 0x510B27F: CertAddCertificateContextToStore (cert.c:287) ==18714== by 0x510A852: CertAddEncodedCertificateToStore (cert.c:65) ==18714== by 0x4EA953F: testCollectionStore (store.c:670) ==18714== by 0x4EB2BF4: func_store (store.c:2790) ==18714== by 0x4EB7F67: run_test (test.h:584) ==18714== by 0x4EB8356: main (test.h:654) ==18714== and several potential leaks, e.g.,: ==18714== 20 bytes in 1 blocks are possibly lost in loss record 53 of 443 ==18714== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==18714== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==18714== by 0x514398B: CryptMemAlloc (main.c:124) ==18714== by 0x511E0A9: CertAddStoreToCollection (collectionstore.c:519) ==18714== by 0x5164B4B: CRYPT_SysOpenStoreW (store.c:592) ==18714== by 0x5164D74: CRYPT_SysOpenStoreA (store.c:644) ==18714== by 0x5165ADF: CertOpenStore (store.c:907) ==18714== by 0x5165B53: CertOpenSystemStoreA (store.c:919) ==18714== by 0x4EA9419: testCollectionStore (store.c:658) ==18714== by 0x4EB2BF4: func_store (store.c:2790) ==18714== by 0x4EB7F67: run_test (test.h:584) ==18714== by 0x4EB8356: main (test.h:654) ==18714== full log attached -- 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 10

[Bug 17913] New: Port royale: black hole instead ocean
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=17913 Summary: Port royale: black hole instead ocean Product: Wine Version: 1.1.18 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: puciek(a)gmail.com Created an attachment (id=20239) --> (http://bugs.winehq.org/attachment.cgi?id=20239) Here should be ocean While playing port royale, and enter "global" mode, instead ocean there is only black color. -- 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.

1 32

[Bug 36623] New: valgrind shows some leaks in ddraw/tests/ddraw7.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36623 Bug ID: 36623 Summary: valgrind shows some leaks in ddraw/tests/ddraw7.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com All of the form: ==31752== 20 bytes in 1 blocks are definitely lost in loss record 194 of 1,726 ==31752== at 0x7BC4C75D: notify_alloc (heap.c:255) ==31752== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==31752== by 0x4A75A4B: DirectDrawCreateClipper (ddraw.c:3274) ==31752== by 0x4A75C0D: ddraw7_CreateClipper (ddraw.c:3309) ==31752== by 0x4DA2139: test_clipper_blt (ddraw7.c:710) ==31752== by 0x4DC439D: func_ddraw7 (ddraw7.c:7183) ==31752== by 0x4DF1F84: run_test (test.h:584) ==31752== by 0x4DF2373: main (test.h:654) ==31752== There's a similar issue in ddraw4 in bug 36343. -- 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 4

[Bug 36631] New: valgrind shows a definite leak in in ddraw/tests/ddraw2.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36631 Bug ID: 36631 Summary: valgrind shows a definite leak in in ddraw/tests/ddraw2.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==8554== 4,096 bytes in 1 blocks are definitely lost in loss record 931 of 958 ==8554== at 0x70746F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==8554== by 0x7070378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0) ==8554== by 0x6C84DC2: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6C86594: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6C8CCCD: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6ABB411: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6C8F89E: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6AA4339: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6AA89E9: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x656BC95: glTexSubImage2D (in /usr/lib/libGL.so.1.2.0) ==8554== by 0x4F3FE80: surface_upload_data (surface.c:1641) ==8554== by 0x4F4D054: surface_load_texture (surface.c:4861) ==8554== by 0x4F4D52E: surface_load_location (surface.c:4954) ==8554== by 0x4F41C25: surface_load (surface.c:2150) ==8554== by 0x4F594DA: texture2d_sub_resource_load (texture.c:730) ==8554== by 0x4F58AE8: wined3d_texture_load (texture.c:539) ==8554== by 0x4E9CEFE: context_apply_blit_state (context.c:2246) ==8554== by 0x4E858D9: arbfp_blit_surface (arb_program_shader.c:7655) ==8554== by 0x4F51910: wined3d_surface_blt (surface.c:6060) ==8554== by 0x4BB146C: ddraw_surface_blt_clipped (surface.c:1387) ==8554== -- 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 35889] New: wine1.6 display fuzzy chinese ttf fonts, but dialog fonts display normal
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=35889 Bug ID: 35889 Summary: wine1.6 display fuzzy chinese ttf fonts, but dialog fonts display normal Product: Wine Version: 1.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gamiljydcome(a)gmail.com Created attachment 47925 --> http://bugs.winehq.org/attachment.cgi?id=47925 fuzzy chinese ttf fonts i am running wine to use tdxw.exe (stock software) for a long time. i installed simsun.ttf to show chinese fonts, before wine 1.5.18 this app disaplay fonts very clearly. but using wine 1.6.x\1.7.x this app display fonts very fuzzy, dialog fonts display normal. my os box is debian7. i have tried disable fontconfig anti-aliasing and wine anti-aliasing, replaced many other ttf fonts, nothing changed. see blow sample photo. how to fix it? -- 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 23

[Bug 38685] New: valgrind shows an invalid read in d3d9/tests/d3d9ex.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=38685 Bug ID: 38685 Summary: valgrind shows an invalid read in d3d9/tests/d3d9ex.c Product: Wine Version: 1.7.44 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ../../../tools/runtest -q -P wine -T ../../.. -M d3d9.dll -p d3d9_test.exe.so d3d9ex && touch d3d9ex.ok ==28064== Invalid read of size 2 ==28064== at 0x4F67EB5: check_gamma_ramps (dc.c:1335) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Address 0x4720000 is 392 bytes inside a block of size 1,712 alloc'd ==28064== at 0x7BC4A9F1: notify_alloc (heap.c:254) ==28064== by 0x7BC4EC94: RtlAllocateHeap (heap.c:1715) ==28064== by 0x4AC1763: wined3d_swapchain_create (swapchain.c:1064) ==28064== by 0x49AA370: swapchain_init (swapchain.c:337) ==28064== by 0x49AA44D: d3d9_swapchain_create (swapchain.c:362) ==28064== by 0x49A3DA1: device_parent_create_swapchain (device.c:3578) ==28064== by 0x4A17107: wined3d_device_init_3d (device.c:911) ==28064== by 0x49A41D0: device_init (device.c:3696) ==28064== by 0x49A609F: d3d9_CreateDeviceEx (directx.c:573) ==28064== by 0x479AE2A: create_device (d3d9ex.c:183) ==28064== by 0x47A13F5: test_user_memory_getdc (d3d9ex.c:1373) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== ==28064== Invalid read of size 2 ==28064== at 0x4F67ECB: check_gamma_ramps (dc.c:1335) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Address 0x4720000 is 392 bytes inside a block of size 1,712 alloc'd ==28064== at 0x7BC4A9F1: notify_alloc (heap.c:254) ==28064== by 0x7BC4EC94: RtlAllocateHeap (heap.c:1715) ==28064== by 0x4AC1763: wined3d_swapchain_create (swapchain.c:1064) ==28064== by 0x49AA370: swapchain_init (swapchain.c:337) ==28064== by 0x49AA44D: d3d9_swapchain_create (swapchain.c:362) ==28064== by 0x49A3DA1: device_parent_create_swapchain (device.c:3578) ==28064== by 0x4A17107: wined3d_device_init_3d (device.c:911) ==28064== by 0x49A41D0: device_init (device.c:3696) ==28064== by 0x49A609F: d3d9_CreateDeviceEx (directx.c:573) ==28064== by 0x479AE2A: create_device (d3d9ex.c:183) ==28064== by 0x47A13F5: test_user_memory_getdc (d3d9ex.c:1373) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== ==28064== Invalid read of size 2 ==28064== at 0x4F67F45: check_gamma_ramps (dc.c:1340) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Address 0x4720000 is 392 bytes inside a block of size 1,712 alloc'd ==28064== at 0x7BC4A9F1: notify_alloc (heap.c:254) ==28064== by 0x7BC4EC94: RtlAllocateHeap (heap.c:1715) ==28064== by 0x4AC1763: wined3d_swapchain_create (swapchain.c:1064) ==28064== by 0x49AA370: swapchain_init (swapchain.c:337) ==28064== by 0x49AA44D: d3d9_swapchain_create (swapchain.c:362) ==28064== by 0x49A3DA1: device_parent_create_swapchain (device.c:3578) ==28064== by 0x4A17107: wined3d_device_init_3d (device.c:911) ==28064== by 0x49A41D0: device_init (device.c:3696) ==28064== by 0x49A609F: d3d9_CreateDeviceEx (directx.c:573) ==28064== by 0x479AE2A: create_device (d3d9ex.c:183) ==28064== by 0x47A13F5: test_user_memory_getdc (d3d9ex.c:1373) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Potentially causing a valgrind crash: Memcheck: mc_main.c:1000 (get_sec_vbits8): Assertion 'n' failed. Memcheck: get_sec_vbits8: no node for address 0x4720000 (0x472000D) host stacktrace: ==28064== at 0x38030875: show_sched_status_wrk (m_libcassert.c:341) ==28064== by 0x38030981: report_and_quit (m_libcassert.c:413) ==28064== by 0x38030A63: vgPlain_assert_fail (m_libcassert.c:479) ==28064== by 0x3800AF24: get_sec_vbits8 (mc_main.c:1000) ==28064== by 0x3800B2FE: get_vbits8 (mc_main.c:812) ==28064== by 0x3800B2FE: mc_LOADVn_slow (mc_main.c:1368) ==28064== by 0x3800D9FF: mc_LOADV16 (mc_main.c:4601) ==28064== by 0x3800D9FF: vgMemCheck_helperc_LOADV16le (mc_main.c:4634) ==28064== by 0xBB643E1: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 28064) ==28064== at 0x4F67EB5: check_gamma_ramps (dc.c:1335) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) -- 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 4