May 2014 - Wine-Bugs - list.winehq.org

[Bug 26119] kernel32/pipe tests show some valgrind warnings

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=26119 --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- A similar issue in hlink/tests/hlink.c: ==11822== Thread 3: ==11822== Syscall param writev(vector[...]) points to uninitialised byte(s) ==11822== at 0x4E9528CC: writev (in /usr/lib/libc-2.18.so) ==11822== by 0x7BC7FE6F: send_request (server.c:213) ==11822== by 0x7BC80001: wine_server_call (server.c:294) ==11822== by 0x7BC80E6E: server_select (server.c:591) ==11822== by 0x7BC8A6F6: NtWaitForMultipleObjects (sync.c:863) ==11822== by 0x7BC8A746: NtWaitForSingleObject (sync.c:872) ==11822== by 0x7BC47912: server_ioctl_file (file.c:1375) ==11822== by 0x7BC48312: NtFsControlFile (file.c:1623) ==11822== by 0x7B8796BF: ConnectNamedPipe (sync.c:1608) ==11822== by 0x469EF26: listen_thread (rpc_transport.c:131) ==11822== by 0x7BC87137: ??? (signal_i386.c:2571) ==11822== by 0x7BC87180: call_thread_func (signal_i386.c:2630) ==11822== by 0x7BC87115: ??? (signal_i386.c:2571) ==11822== by 0x7BC8E560: start_thread (thread.c:428) ==11822== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==11822== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==11822== Address 0x51be59c is on thread 1's stack ==11822== Uninitialised value was created by a stack allocation ==11822== at 0x7B8795C0: ConnectNamedPipe (sync.c:1594) ==11822== -- 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.

May 31, 2014

[Bug 31744] Multiple GFWL (Games For Windows Live) 3.5 games crash on startup due to incomplete Windows LiveID install (Street Fighter X Tekken)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=31744 --- Comment #8 from Anastasius Focht <focht(a)gmx.net> --- Hello Nikolay, --- quote --- RegGetValueW() already returns Win32 error, no need to map it. I'll try to add a mapping for 0x00000002 NTSTATUS anyway. --- quote --- Yes, that call to 'LsaNtStatusToWinError' looks fishy. Anyway, even with _some_ mapping it doesn't change the end result, so don't bother with it. The registry data should have been present in first place (broken installer). Here is a good article about error code formats/conversion/mapping: http://jpassing.com/2007/08/20/error-codes-win32-vs-hresult-vs-ntstatus/ 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.

May 31, 2014

[Bug 36623] New: valgrind shows some leaks in ddraw/tests/ddraw7.c

by wine-bugs＠winehq.org

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.

May 31, 2014

[Bug 31744] Multiple GFWL (Games For Windows Live) 3.5 games crash on startup due to incomplete Windows LiveID install (Street Fighter X Tekken)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=31744 --- Comment #7 from Nikolay Sivov <bunglehead(a)gmail.com> --- This looks strange: --- 002b:Call advapi32.RegGetValueW(80000002,01517e28 L"SOFTWARE\\Microsoft\\IdentityCRL",01517e68 L"TargetDir",0000ffff,0033ee78,0033ee7c,0033ee74) ret=015cc368 002b:Ret advapi32.RegGetValueW() retval=00000002 ret=015cc368 002b:Call advapi32.LsaNtStatusToWinError(00000002) ret=015cc37f 002b:fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 00000002 002b:Ret advapi32.LsaNtStatusToWinError() retval=0000013d ret=015cc37f --- RegGetValueW() already returns Win32 error, no need to map it. I'll try to add a mapping for 0x00000002 NTSTATUS anyway. -- 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.

May 31, 2014

[Bug 36622] New: activation.dll loading failed in origin

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36622 Bug ID: 36622 Summary: activation.dll loading failed in origin Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: paulthetall(a)gmail.com I used the two patches (Qt5Network + the EA Origin needs job objects one) so download speed is fine and no proxy hang stuff. However I still can't launch any game. I get a Activation dll loading failed message on every attempt to play a game. I am so close....please help. OSX 10.8.5 (Macbook) + OSX 10.9.3 (iMac with Nvidia 640M + Macbook Nvidia 9400M + iMac AMD Radeon 6770M) Test debug says this: fixme:msg:ChangeWindowMessageFilterEx 0x30074 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x30074 112 1 0x0 fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:msg:ChangeWindowMessageFilterEx 0x10096 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x10096 112 1 0x0 fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:msg:ChangeWindowMessageFilterEx 0x100a6 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100a6 112 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100b0 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100b0 112 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100ba 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100ba 112 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100c4 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100c4 112 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100ce 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100ce 112 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100d8 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100d8 112 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x2009c 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x2009c 112 1 0x0 fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0xf8fd99c 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0xf8fd73c 1 C) semi-stub fixme:netprofm:list_manager_GetConnectivity 0x1e6888, 0x32d658 fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot fixme:toolhelp:Heap32ListFirst : stub fixme:msg:ChangeWindowMessageFilterEx 0x100f2 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100f2 112 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100f8 4a 1 0x0 fixme:msg:ChangeWindowMessageFilterEx 0x100f8 112 1 0x0 err:ole:CoCreateInstance apartment not initialised fixme:shell:IShellLinkW_fnGetPath (0x21d8c0): WIN32_FIND_DATA is not yet filled. fixme:heap:HeapSetInformation 0x0 1 0x0 0 fixme:system:SetProcessDPIAware stub! fixme:ntdll:server_ioctl_file Unsupported ioctl 110004 (device=11 access=0 func=1 method=0) fixme:ntdll:server_ioctl_file Unsupported ioctl 110004 (device=11 access=0 func=1 method=0) fixme:netprofm:list_manager_GetConnectivity 0x1e6888, 0x32d658 err:ole:CoCreateInstance apartment not initialised fixme:shell:IShellLinkW_fnGetPath (0x3acf1a0): WIN32_FIND_DATA is not yet filled. When more info is needed let me know. Many thanks! -- 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.

May 31, 2014

[Bug 36261] valgrind shows a use after free in d3d_device_inner_Release() ddraw/tests/ddraw{4,7}.c

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36261 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|valgrind shows a use after |valgrind shows a use after |free in |free in |d3d_device7_Release() |d3d_device_inner_Release() |ddraw/tests/ddraw{4,7}.c |ddraw/tests/ddraw{4,7}.c -- 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.

May 31, 2014

[Bug 36261] valgrind shows a use after free in d3d_device7_Release() ddraw/tests/ddraw{4,7}.c

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36261 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|valgrind shows a use after |valgrind shows a use after |free in |free in |ddraw/tests/ddraw4.c |d3d_device7_Release() | |ddraw/tests/ddraw{4,7}.c --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- The original problem also occurs in ddraw7's tests: ==29087== Invalid write of size 4 ==29087== at 0x4B962A8: d3d_device_inner_Release (device.c:319) ==29087== by 0x4B963D9: d3d_device7_Release (device.c:336) ==29087== by 0x4AD6C8B: test_coop_level_d3d_state (ddraw7.c:913) ==29087== by 0x4AF73A2: func_ddraw7 (ddraw7.c:7184) ==29087== by 0x4B24F84: run_test (test.h:584) ==29087== by 0x4B25373: main (test.h:654) ==29087== Address 0x48b7540 is 112 bytes inside a block of size 160 free'd ==29087== at 0x7BC4C7AA: notify_free (heap.c:263) ==29087== by 0x7BC510EF: RtlFreeHeap (heap.c:1762) ==29087== by 0x4B889F9: ddraw_destroy (ddraw.c:441) ==29087== by 0x4B88B01: ddraw7_Release (ddraw.c:459) ==29087== by 0x4BAEC45: ddraw_surface_release_iface (surface.c:558) ==29087== by 0x4BAED19: ddraw_surface7_Release (surface.c:602) ==29087== by 0x4B96249: d3d_device_inner_Release (device.c:316) ==29087== by 0x4B963D9: d3d_device7_Release (device.c:336) ==29087== by 0x4AD6C8B: test_coop_level_d3d_state (ddraw7.c:913) ==29087== by 0x4AF73A2: func_ddraw7 (ddraw7.c:7184) ==29087== by 0x4B24F84: run_test (test.h:584) ==29087== by 0x4B25373: main (test.h:654) ==29087== -- 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.

May 31, 2014

[Bug 36261] valgrind shows a use after free in ddraw/tests/ddraw4.c

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36261 --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- Also: ==26415== Invalid write of size 4 ==26415== at 0x4B962A8: d3d_device_inner_Release (device.c:319) ==26415== by 0x4B9647B: d3d_device3_Release (device.c:345) ==26415== by 0x4AAFA09: test_coop_level_d3d_state (ddraw4.c:994) ==26415== by 0x4AD1B87: func_ddraw4 (ddraw4.c:7455) ==26415== by 0x4B24F84: run_test (test.h:584) ==26415== by 0x4B25373: main (test.h:654) ==26415== Address 0x482ea30 is 112 bytes inside a block of size 160 free'd ==26415== at 0x7BC4C7AA: notify_free (heap.c:263) ==26415== by 0x7BC510EF: RtlFreeHeap (heap.c:1762) ==26415== by 0x4B889F9: ddraw_destroy (ddraw.c:441) ==26415== by 0x4B88C0C: ddraw4_Release (ddraw.c:472) ==26415== by 0x4BAEC45: ddraw_surface_release_iface (surface.c:558) ==26415== by 0x4BAEDED: ddraw_surface4_Release (surface.c:617) ==26415== by 0x4B96249: d3d_device_inner_Release (device.c:316) ==26415== by 0x4B9647B: d3d_device3_Release (device.c:345) ==26415== by 0x4AAFA09: test_coop_level_d3d_state (ddraw4.c:994) ==26415== by 0x4AD1B87: func_ddraw4 (ddraw4.c:7455) ==26415== by 0x4B24F84: run_test (test.h:584) ==26415== by 0x4B25373: main (test.h:654) ==26415== ==26415== Warning: client syscall munmap tried to modify addresses 0x81d30000-0x81d30fff ==26415== Invalid read of size 4 ==26415== at 0x400B950: memcpy (vg_replace_strmem.c:908) ==26415== by 0x4EABBB8: wined3d_device_set_ps_consts_f (device.c:2496) ==26415== by 0x4F37473: wined3d_stateblock_apply (stateblock.c:984) ==26415== by 0x4B8A1ED: ddraw_set_cooperative_level (ddraw.c:951) ==26415== by 0x4B8A5E2: ddraw7_SetCooperativeLevel (ddraw.c:1010) ==26415== by 0x4B888F3: ddraw_destroy (ddraw.c:420) ==26415== by 0x4B88C0C: ddraw4_Release (ddraw.c:472) ==26415== by 0x4AB0162: test_surface_interface_mismatch (ddraw4.c:1088) ==26415== by 0x4AD1B8C: func_ddraw4 (ddraw4.c:7456) ==26415== by 0x4B24F84: run_test (test.h:584) ==26415== by 0x4B25373: main (test.h:654) ==26415== Address 0xa174000 is 880 bytes inside a block of size 65,536 alloc'd ==26415== at 0x7BC4C75D: notify_alloc (heap.c:255) ==26415== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==26415== by 0x4F38C30: state_init (stateblock.c:1324) ==26415== by 0x4F38D09: stateblock_init (stateblock.c:1346) ==26415== by 0x4F38F8E: wined3d_stateblock_create (stateblock.c:1403) ==26415== by 0x4B8A024: ddraw_set_cooperative_level (ddraw.c:914) ==26415== by 0x4B8A5E2: ddraw7_SetCooperativeLevel (ddraw.c:1010) ==26415== by 0x4B888F3: ddraw_destroy (ddraw.c:420) ==26415== by 0x4B88C0C: ddraw4_Release (ddraw.c:472) ==26415== by 0x4AB0162: test_surface_interface_mismatch (ddraw4.c:1088) ==26415== by 0x4AD1B8C: func_ddraw4 (ddraw4.c:7456) ==26415== by 0x4B24F84: run_test (test.h:584) ==26415== by 0x4B25373: main (test.h:654) ==26415== ==26415== Invalid read of size 4 ==26415== at 0x400B95A: memcpy (vg_replace_strmem.c:908) ==26415== by 0x4EABBB8: wined3d_device_set_ps_consts_f (device.c:2496) ==26415== by 0x4F37473: wined3d_stateblock_apply (stateblock.c:984) ==26415== by 0x4B8A1ED: ddraw_set_cooperative_level (ddraw.c:951) ==26415== by 0x4B8A5E2: ddraw7_SetCooperativeLevel (ddraw.c:1010) ==26415== by 0x4B888F3: ddraw_destroy (ddraw.c:420) ==26415== by 0x4B88C0C: ddraw4_Release (ddraw.c:472) ==26415== by 0x4AB0162: test_surface_interface_mismatch (ddraw4.c:1088) ==26415== by 0x4AD1B8C: func_ddraw4 (ddraw4.c:7456) ==26415== by 0x4B24F84: run_test (test.h:584) ==26415== by 0x4B25373: main (test.h:654) ==26415== Address 0xa174008 is 888 bytes inside a block of size 65,536 alloc'd ==26415== at 0x7BC4C75D: notify_alloc (heap.c:255) ==26415== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==26415== by 0x4F38C30: state_init (stateblock.c:1324) ==26415== by 0x4F38D09: stateblock_init (stateblock.c:1346) ==26415== by 0x4F38F8E: wined3d_stateblock_create (stateblock.c:1403) ==26415== by 0x4B8A024: ddraw_set_cooperative_level (ddraw.c:914) ==26415== by 0x4B8A5E2: ddraw7_SetCooperativeLevel (ddraw.c:1010) ==26415== by 0x4B888F3: ddraw_destroy (ddraw.c:420) ==26415== by 0x4B88C0C: ddraw4_Release (ddraw.c:472) ==26415== by 0x4AB0162: test_surface_interface_mismatch (ddraw4.c:1088) ==26415== by 0x4AD1B8C: func_ddraw4 (ddraw4.c:7456) ==26415== by 0x4B24F84: run_test (test.h:584) ==26415== by 0x4B25373: main (test.h:654) ==26415== there's a valgrind assertion failure, after all of this, which these issues could be causing: memcheck: mc_main.c:1003 (get_sec_vbits8): Assertion 'n' failed. Memcheck: get_sec_vbits8: no node for address 0xA174000 (0xA17400F) ==26415== at 0x3804CD81: report_and_quit (m_libcassert.c:279) ==26415== by 0x3804CEA9: vgPlain_assert_fail (m_libcassert.c:359) ==26415== by 0x380255EE: get_sec_vbits8 (mc_main.c:1003) ==26415== by 0x38000585: mc_LOADVn_slow (mc_main.c:813) ==26415== by 0x38027616: vgMemCheck_helperc_LOADV32le (mc_main.c:4482) ==26415== by 0x88DFDA8C: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==26415== at 0x400B95A: memcpy (vg_replace_strmem.c:908) ==26415== by 0x4EABBB8: wined3d_device_set_ps_consts_f (device.c:2496) ==26415== by 0x4F37473: wined3d_stateblock_apply (stateblock.c:984) ==26415== by 0x4B8A1ED: ddraw_set_cooperative_level (ddraw.c:951) ==26415== by 0x4B8A5E2: ddraw7_SetCooperativeLevel (ddraw.c:1010) ==26415== by 0x4B888F3: ddraw_destroy (ddraw.c:420) ==26415== by 0x4B88C0C: ddraw4_Release (ddraw.c:472) ==26415== by 0x4AB0162: test_surface_interface_mismatch (ddraw4.c:1088) ==26415== by 0x4AD1B8C: func_ddraw4 (ddraw4.c:7456) ==26415== by 0x4B24F84: run_test (test.h:584) ==26415== by 0x4B25373: main (test.h:654) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. -- 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.

May 31, 2014

[Bug 36340] valgrind shows several warnings in ddraw/tests/ddraw2.c

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=36340 --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- ==24782== Invalid read of size 4 ==24782== at 0x4ECE803: update_heap_entry (glsl_shader.c:905) ==24782== by 0x4ECE93C: shader_glsl_update_float_vertex_constants (glsl_shader.c:939) ==24782== by 0x4EAAF2A: wined3d_device_set_vs_consts_f (device.c:2297) ==24782== by 0x4F372E0: wined3d_stateblock_apply (stateblock.c:962) ==24782== by 0x4B8A1ED: ddraw_set_cooperative_level (ddraw.c:951) ==24782== by 0x4B8A75C: ddraw2_SetCooperativeLevel (ddraw.c:1028) ==24782== by 0x4A88F26: test_coop_level_create_device_window (ddraw2.c:457) ==24782== by 0x4AAA2F2: func_ddraw2 (ddraw2.c:6562) ==24782== by 0x4B24F84: run_test (test.h:584) ==24782== by 0x4B25373: main (test.h:654) ==24782== Address 0xa128000 is 48,344 bytes inside a block of size 65,544 alloc'd ==24782== at 0x7BC4C75D: notify_alloc (heap.c:255) ==24782== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==24782== by 0x4EDF5F4: constant_heap_init (glsl_shader.c:6412) ==24782== by 0x4EDF9BB: shader_glsl_alloc (glsl_shader.c:6481) ==24782== by 0x4EA56CD: wined3d_device_init_3d (device.c:882) ==24782== by 0x4B89381: ddraw_attach_d3d_device (ddraw.c:591) ==24782== by 0x4B895B9: ddraw_create_swapchain (ddraw.c:634) ==24782== by 0x4B8A124: ddraw_set_cooperative_level (ddraw.c:934) ==24782== by 0x4B8A75C: ddraw2_SetCooperativeLevel (ddraw.c:1028) ==24782== by 0x4A88F26: test_coop_level_create_device_window (ddraw2.c:457) ==24782== by 0x4AAA2F2: func_ddraw2 (ddraw2.c:6562) ==24782== by 0x4B24F84: run_test (test.h:584) ==24782== by 0x4B25373: main (test.h:654) ==24782== -- 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.

May 31, 2014

[Bug 36489] Fate:Stay/Night performance regression

by wine-bugs＠winehq.org

http://bugs.winehq.org/show_bug.cgi?id=36489 --- Comment #9 from Dennis Borisevich <elfmax(a)tut.by> --- Created attachment 48671 --> http://bugs.winehq.org/attachment.cgi?id=48671 +ddraw log with OpenGL enabled Attached gzip'd log with OpenGL DirectDraw rendering. On both startups I did simple things: - waited for main menu to open - loaded a game - picked through some lines of text in VN - closed game - CTRL-C stopped the game from console ( always like that, it does not close wine window, although seems to exit ) -- 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.

May 31, 2014