http://bugs.winehq.org/show_bug.cgi?id=19561
Summary: Very large memory leak when doing overlapped reads
Product: Wine
Version: 1.1.26
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wineserver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ronfischler(a)gmail.com
Created an attachment (id=22796)
--> (http://bugs.winehq.org/attachment.cgi?id=22796)
Program compiled and ready to run using mingw
WINE is buffering serial ports which is in conflict with using overlapped
reads. Additionally, when using overlapped reads on a serial port, there is a
large memory leak. Every time we receive a block of data on the port, (say 800
bytes in our case,) wineserver allocates many pages on the heap and does not
free them afterwards. We are seeing as many as 21 pages lost to the heap every
time we read a small block of data.
My company is creating a Monitor & Control product that works through serial
ports, and we want it to be able to run on Linux netbooks (using USB to serial
port adapters.) This memory leak is the only thing holding us up. The memory
leak is too large for us to recommend to customers that our application can be
used on Linux platforms using WINE.
We are including an attachment for a small program that captures the leak. The
problem is a result of our call to readfile() in the do-while loop. It is using
the overlappedRead feature. Every time this Win32 function call is made, 84K
bytes disappears forever.
-Ron F.
--
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=54858
Bug ID: 54858
Summary: Multiple games call for
"Windows.System.DispatcherQueue" (Tannenberg, The Last
Stand: Aftermath, The Long Dark)
Product: Wine
Version: 8.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Lots of
0e8c:fixme:combase:RoGetActivationFactory (L"Windows.System.DispatcherQueue",
{00000035-0000-0000-c000-000000000046}, 00007FEEE4A0FA00): semi-stub
0e8c:err:combase:RoGetActivationFactory Failed to find library for
L"Windows.System.DispatcherQueue"
8.6-29-ga19c1ff1697
--
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=48746
Bug ID: 48746
Summary: Null_DC stops with error on Emulator Startup (not
opening the application)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: apphelp
Assignee: wine-bugs(a)winehq.org
Reporter: starfirehyper(a)gmail.com
Distribution: ---
Hello,
I am having issues with Wine and Null DC
I do have Crossover on a Chromebook, but whatever I start the emulator (not
opening the application) I get a error that tells me " The program (the full
name of the exe) has encountered a serious problem and needs to close." The
link on the error wasn't very helpful. (I am running nullDC 1.0.4 and I don't
know what is causing it)
Thank you and good bye.
Have a nice day! :)
--
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=48771
Bug ID: 48771
Summary: SoulWorker from Official Launcher
Product: Wine
Version: 5.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: full01(a)linuxmail.org
Distribution: ---
I can't start the game from the Official Launcher. The launcher starts with
Wine-staging but I get the error (The Directory is Invalid) when I try to start
the game client.
The game worked flawlessly before they changed the launcher.
I think the problem is the second launcher called "Soulworkerlauncher.exe".
The game is free to play: https://en.soulworker.gameforge.com/landingpage/
--
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=53407
Bug ID: 53407
Summary: Hogia Hemekonomi Missing date picker widget
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)jonass.user.lysator.liu.se
Distribution: ---
Created attachment 72799
--> https://bugs.winehq.org/attachment.cgi?id=72799
How the calendar widget looks when run on Windows XP.
When showing transactions there is a date entry field where the user can enter
a date. Or press "enter" to get a date picker widget. The widget seems to be
missing in Wine.
To reproduce:
- Run the software like "wine Hemeko.exe"
- There will be dialogue asking about number format, click Yes.
- On first run you get an intro (or error see Bug 53384). If error, just
dismiss. If intro, press "Återgå till Hemekonomi" to dismiss.
- Click "Arkiv" and "Ny" to create a new database to work with. When asked
"Ange namnet på den nya databasen" enter something like "foo.mdb" and click OK.
- Click "Fortsätt med Hemekonomi" to dismiss setup wizard.
- Press CTRL-K or click on icon Kontoutdrag.
- Click OK.
- Use mouse to set focus on entry field in lower right corner called "Fr o m"
- Press enter.
- See Program Error.
On subsequent runs click Arkiv/Öppna instead to use the existing foo.mdb
database.
--
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=42882
Bug ID: 42882
Summary: rs232 port access no working with ubuntu 17.10 worked
fine with previous versions of ubuntu
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: arcadeshopper(a)gmail.com
Distribution: ---
I am able to connect to the serial port via applications in wine but there is
never any data received.
I can communicate outside of wine without issue using minicom.
I am using a ftdi usb to serial adapter that worked fine in previous versions
of ubuntu. I am having this problems with all relases of wine I have tried
including the default ubuntu package and 2.4 from the 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=55138
Bug ID: 55138
Summary: msys2: bash.exe is not able to fork/start another
process.
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 74697
--> https://bugs.winehq.org/attachment.cgi?id=74697
allocation stacks in parent and child bash.exe
This is a followup to bug 47808.
If I understand it right, bug 47808 was primarily about native libraries
getting called at a win32 stack which was not yet committed.
Those native libraries then jumped over the guard page, therefore the stack
got not grown, instead a crash reported.
This aspect was fixed by using the syscall interface and
therefore bug 47808 was closed.
But there is another issue that causes a msys2-forked process crashing,
because after the stack was grown it still misses the PAGE_READWRITE flags.
For this Zeb Figura included in the first attachement to bug 47808
"always expand the stack if within the stack reserve"
a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE"
to the page that gets the VPROT_GUARD removed in grow_thread_stack.
This modification still enables a forked process to run.
The issue can be reproduced with an unmodified wine by just
- running msys2 bash.exe interactively
- then trying to start e.g. notepad from it.
Attached file shows the stack when the stack gets allocated
- in a working msys2-parent process and
- in a failing msys2-forked child process.
Therefore it looks like the forked stack get really setup differently,
but it is still not clear if or when this memory gets the READ/WRITE
added in native windows.
--
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=37131
Bug ID: 37131
Summary: Clang Static Analyzer: Division by zero
Product: Wine
Version: 1.7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukebenes(a)hotmail.com
Clang Static Analyzer identifies Division by zero
File: dlls/winex11.drv/palette.c
Location: line 601, column 43
Description: Division by zero
#define NB_RESERVED_COLORS 20
...
static void X11DRV_PALETTE_FillDefaultColors(....)
{
...
int i = 0, idx = 0;
int red, no_r, inc_r;
...
if (palette_size <= NB_RESERVED_COLORS)
return;
while (i*i*i < (palette_size - NB_RESERVED_COLORS)) i++;
no_r = no_g = no_b = --i;
...
inc_r = (255 - NB_COLORCUBE_START_INDEX)/no_r;
//Clang: Division by zero
...
}
The code will continue executing if the palette_size variable is larger than or
equal to 21. With the value 21, the 'i' variable will be first incremented by
one and then decremented by one. As a result, the 'i' variable will remain
equal to zero, which will cause the division-by-zero 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.
http://bugs.winehq.org/show_bug.cgi?id=31212
Bug #: 31212
Summary: Some VST instruments crash when reloaded in Mixcraft
Product: Wine
Version: 1.5.8
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: s_chriscollins(a)hotmail.com
Classification: Unclassified
In Mixcraft, some VST instruments crash when loaded a second time on a track.
However, the same instruments work fine when loaded for the first time on a
track. The following can be reproduced easily in Mixcraft:
1. Start Mixcraft and select "Build Virtual Instrument Tracks" from the "New
Project" window.
2. Click on the keyboard icon next to the first track name, which will bring up
the instrument selection window.
3. Select "<VSTi Instruments>" from the left pane and then "Messiah" from the
right pane. This sets the track to use the Messiah VSTi synth.
4. Now select "Acoustica Instruments" from the right pane.
5. Once again, select "Messiah" from the right pane. Mixcraft will pop up an
error box with the title "An instrument has crashed" containing the following
text: "A crash has been detected in the instrument "Messiah." This plug-in has
been muted. We recommend you save your project and re-start Mixcraft to avoid
losing your work."
Unfortunately, no helpful terminal output seems to be generated in relation to
the plugin crash. I have provided more detailed notes on VST behavior in
Mixcraft here:
https://docs.google.com/document/d/1YEPh0mkd_ip1whAJXcRIl4HYny5D8LSeGo3qgzV…
** My System **
OS: Kubuntu 12.04 64-bit w/ KDE SC 4.8.4
Motherboard: ASRock X58 Extreme3 (Intel X58 chipset)
CPU: Intel Core i7 (2.8 GHz quad-core)
RAM: 12GB DDR3
Video: Dell NVIDIA GeForce 7800 GTX w/ 256 MB RAM (PCI Express)
Sound Card #1: Sound Blaster Audigy 2 ZS Gold
Sound Card #2: Echo Gina3G
Linux Kernel: 3.2.0-26-generic
NVIDIA video driver: 302.17
Screen Resolution: 1280 x 960
--
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=55019
Bug ID: 55019
Summary: kernel32:process - Accents cause test_Environment() to
fail on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:process - Accents cause test_Environment() to fail on Windows:
process.c:1267: Test failed: Parent-env string CI_COMMIT_AUTHOR=Bernhard Klbl
<besentv(a)gmail.com> isn't in child process
process.c:1267: Test failed: Parent-env string CI_COMMIT_DESCRIPTION=
Signed-off-by: Bernhard Klbl <besentv(a)gmail.com> isn't in child process
process.c:1267: Test failed: Parent-env string CI_COMMIT_MESSAGE=mf/tests:
Remove duplicate call to MFStartup().
Signed-off-by: Bernhard Klbl <besentv(a)gmail.com>
isn't in child process
process.c:1292: Test failed: Child-env string CI_COMMIT_AUTHOR=Bernhard K"lbl
<besentv(a)gmail.com> isn't in parent process
process.c:1292: Test failed: Child-env string CI_COMMIT_DESCRIPTION=
Signed-off-by: Bernhard K"lbl <besentv(a)gmail.com> isn't in parent process
process.c:1292: Test failed: Child-env string CI_COMMIT_MESSAGE=mf/tests:
Remove duplicate call to MFStartup().
Signed-off-by: Bernhard K"lbl <besentv(a)gmail.com>
isn't in parent process
See https://test.winehq.org/data/patterns.html#kernel32:process
These failures happen in about 15% of the runs and in all of them the
environment variable was supposed to contain an accent.
This also explains why the failures:
* Are always about the GitLab environment variables: in our regular test
configurations environment variables don't contain accents.
* Only happen on the GitLab CI Windows test VM: this VM is the only one where
the environment variables change from one run to the next, mostly due to
CI_COMMIT_XXX.
* Always happen in both the 32- and 64-bit tests of a given build.
--
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.