https://bugs.winehq.org/show_bug.cgi?id=56876
Bug ID: 56876
Summary: Paint Tool SAIv2 VirtualAlloc invalid address on
commit
Product: Wine
Version: 9.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: cromachina(a)gmail.com
Distribution: ---
When using Paint Tool SAIv2 (any recent version, Preview.2024.05.22 for
example), the program will often start emitting errors when a few files are
opened and random scatter brushes are selected (brushes that open bitmap files
to draw themselves). After this point, the program can quickly become unstable
and inoperable, further opening of files may fail, and attempting to save files
in this state may cause file corruption. I've never experienced this issue when
using SAI in Windows 10, so I think it is more likely an issue within Wine than
SAI itself.
What I think is causing the errors:
Although the errors seems to be related to files being opened, it seems to be
caused by subsequent memory allocations. Checking SAI's error log, it says
"!WinError(487): Invalid address." When running with WINDDEBUG=+all, I found
that an invalid address error (0x000001E7, 487) is reported after the program
attempts to commit a page of memory with VirtualAlloc:
For this particular example, the program likely attempted to write to a
reserved address 177FFF8, so then a SEH for EXCEPTION_ACCESS_VIOLATION occured.
The SEH then attempted to commit 177FFF8 with VirtualAlloc, but it failed, and
then GetLastError returned 000001e7 ERROR_INVALID_ADDRESS:
38822.915:0020:01b8:Call
KERNEL32.VirtualAlloc(0177fff8,00001000,00001000,00000004) ret=14019f0d2
38822.915:0020:01b8:Ret KERNEL32.VirtualAlloc() retval=00000000 ret=14019f0d2
This should have been a valid address to commit, which should have returned the
next lowest page, for example 177f000.
The internal call to ntdll.NtAllocateVirtualMemory returned c0000019, which is
STATUS_NOT_MAPPED_VIEW.
Looking earlier into the log, I can confirm that the region should have indeed
been reserved:
38744.422:0020:0024:Call
KERNEL32.VirtualAlloc(00000000,00400000,00002000,00000004) ret=1401a0a0e
38744.422:0020:0024:Ret KERNEL32.VirtualAlloc() retval=01380000 ret=1401a0a0e
This region 01380000 - 1780000 contains address 177FFF8 (8 bytes from the end
of the last page).
I could not find any indication that this reserved region is ever freed by
VirtualFree. Therefore, I think that this may indicate that the views_tree used
by find_view had become damaged somehow:
https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/unix/virtual.c#L…
I've compressed the massive log file, but it's still too large to attach, so
I've uploaded it here:
https://mega.nz/file/ET5S1LzY#WyVvta3n4QxeLjmzkyJqWmU5ZdgODWh4jILvNg32_rE
--
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=55155
Bug ID: 55155
Summary: Telegram can not be run in latest version wine, but ok
in wine6.0.4
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 398063392(a)qq.com
Distribution: ---
the Telegram which I used is unpacked from
https://updates.tdesktop.com/tx64/tportable-x64.4.8.3.zip
--
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=57692
Bug ID: 57692
Summary: No context menu in Reason (DAW)
Product: Wine
Version: 10.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: schroedingerscat(a)disroot.org
Distribution: ---
The context menu in ReasonStudio's DAW Reason is broken. The regression was
introduced with v10.0-rc6 as context menus worked fine until Wine v10.0-rc5.
To reproduce, following the installation procedure from here (under Additional
Notes): https://appdb.winehq.org/objectManager.php?sClass=version&iId=42495
Then after starting the app and finishing the initial configuration dialogues,
try to right-click with your mouse anywhere in the application to open the
context menu. Nothing will happen. There's also nothing being logged when
trying to open the context menu.
--
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=56530
Bug ID: 56530
Summary: Final Fantasy XI Online: Memory leak when Wine is
built with CFLAGS="-g -mno-avx".
Product: Wine
Version: 8.13
Hardware: x86-64
URL: https://web.archive.org/web/20210810150839/http://www.
playonline.com/ff11eu/download/media/install_win.html
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: chiitoo(a)gentoo.org
Regression SHA1: c065b4fe0b3622e0c737a4c7c1c514273ad2d8a7
Distribution: ---
After c065b4fe0b3 [1], a memory leak can be seen in Final Fantasy XI Online,
but only when building with
CFLAGS="-g"
instead of
CFLAGS="-march=znver4 -O2 -pipe -mindirect-branch=thunk -mno-avx"
----
err:d3d:wined3d_debug_callback 01DBBCF8: "GL_OUT_OF_MEMORY in glGetTexImage".
----
Nothing too specific needs to be done, aside from simply logging in to the
game, and standing still, which will make the address space fill up in a few
minutes (some in-game area requirements may be present, or at least some make
it happen faster than others).
Thank you!
1.
https://source.winehq.org/git/wine.git/commitdiff/c065b4fe0b3622e0c737a4c7c…
--
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=57766
Bug ID: 57766
Summary: Win3_BIOS most likely should be Win32_BIOS instead
Product: Wine
Version: 10.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wmi&wbemprox
Assignee: wine-bugs(a)winehq.org
Reporter: depaoli.renzo(a)gmail.com
Distribution: ---
wine-10.0-rc6/dlls/wbemprox/tests/query.c
Line #93 states
L"SELECT * FROM Win3_BIOS WHERE NAME <> NULL",
It seems likely that this was intended instead
L"SELECT * FROM Win32_BIOS WHERE NAME <> NULL",
e.g. the line #94 states
L"SELECT * FROM Win32_BIOS WHERE NULL = NAME",
--
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=57794
Bug ID: 57794
Summary: WinHTTP implementation assumes HTTP response has a
status text
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winhttp
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)sai.navy
Distribution: ---
When the HTTP server only provides a status code, e.g. 'HTTP/1.0 200', Wine's
WinHttpReceiveResponse() fails with ERROR_WINHTTP_INVALID_SERVER_RESPONSE.
The exact problem seems to be here:
https://github.com/wine-mirror/wine/blob/55a3a7ee77844258fb480c3c11747893fc…
This is incongruent with Microsoft's WinHTTP implementation and also generally
a weird requirement that doesn't match real-world usage.
--
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=57360
Bug ID: 57360
Summary: Wrong Combobox dropdown in 7zFM
Product: Wine
Version: 9.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: kyle.kcsoftwares(a)gmail.com
Distribution: ---
Created attachment 77328
--> https://bugs.winehq.org/attachment.cgi?id=77328
Too large drop down
Install 7z 24.08
in 7zFM, dropdown combobox => Too large with many "empty" lines
--
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=27245
Summary: Internet Settings security zones not i18n-ed
Product: Wine
Version: 1.3.20
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: frederic.delanoy(a)gmail.com
Created an attachment (id=34829)
--> (http://bugs.winehq.org/attachment.cgi?id=34829)
Internet Settings screenshot (French)
In the control panel (wine control), tab "Security", the security zones and
their associates descriptions aren't translatable.
They seem to be hardcoded in dll/urlmon/urlmon.inf
--
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=53644
Bug ID: 53644
Summary: vbscript can not compile classes with lists of private
/ public / dim declarations
Product: Wine
Version: 7.16
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: jsm174(a)gmail.com
I am working on porting Visual Pinball to MacOS. I am using the vbscript engine
from Wine and just found out that it is having issues compiling classes that
have lists of private / public declarations.
For example:
Class FlipperPolarity
Public DebugOn, Enabled
private Flipper, FlipperStart,FlipperEnd, FlipperEndY, LR,
PartialFlipCoef
Private Balls(20), balldata(20)
dim PolarityIn, PolarityOut
dim VelocityIn, VelocityOut
dim YcoefIn, YcoefOut
.
.
.
End Class
To get this to compile, I had to split everything to a separate line. I also
had to switch the arrays to dim
Class FlipperPolarity
Public DebugOn
Public Enabled
private Flipper
private FlipperStart
private FlipperEnd
private FlipperEndY
private LR
private PartialFlipCoef
dim Balls(20)
dim balldata(20)
dim PolarityIn
dim PolarityOut
dim VelocityIn
dim VelocityOut
dim YcoefIn
dim YcoefOut
.
.
.
End Class
I think an update is required in parser.y, but I'm not sure yet:
ClassBody
: /* empty */ { $$ = new_class_decl(ctx); }
| FunctionDecl { $$ =
add_class_function(ctx, new_class_decl(ctx), $1); CHECK_ERROR; }
| FunctionDecl StSep ClassBody { $$ =
add_class_function(ctx, $3, $1); CHECK_ERROR; }
/* FIXME: We should use DimDecl here to support arrays, but that conflicts
with PropertyDecl. */
| Storage tIdentifier { dim_decl_t *dim_decl =
new_dim_decl(ctx, $2, FALSE, NULL); CHECK_ERROR;
$$ = add_dim_prop(ctx,
new_class_decl(ctx), dim_decl, $1); CHECK_ERROR; }
| Storage tIdentifier StSep ClassBody { dim_decl_t *dim_decl =
new_dim_decl(ctx, $2, FALSE, NULL); CHECK_ERROR;
$$ = add_dim_prop(ctx, $4,
dim_decl, $1); CHECK_ERROR; }
| tDIM DimDecl { $$ = add_dim_prop(ctx,
new_class_decl(ctx), $2, 0); CHECK_ERROR; }
| tDIM DimDecl StSep ClassBody { $$ = add_dim_prop(ctx, $4,
$2, 0); CHECK_ERROR; }
| PropertyDecl { $$ =
add_class_function(ctx, new_class_decl(ctx), $1); CHECK_ERROR; }
| PropertyDecl StSep ClassBody { $$ =
add_class_function(ctx, $3, $1); CHECK_ERROR; }
--
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.