http://bugs.winehq.org/show_bug.cgi?id=20351
Summary: Keyword corral crashes : Unhandled Exception:
OutOfMemoryException.
Product: Wine
Version: 1.1.28
Platform: PC
URL: http://www.johncow.com/brand-new-free-keyword-corral-t
ool-by-john-cow-dot-com/
OS/Version: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
This is a regression, the app used to crash a bit later in LsaLookupNmaes2 (see
http://bugs.winehq.org/show_bug.cgi?id=16418) , but now crashes rightaway:
27ebfdb879ad4ddccbef5a864ea6928c7b80ccc1 is first bad commit
commit 27ebfdb879ad4ddccbef5a864ea6928c7b80ccc1
Author: Dmitry Timoshkov <dmitry(a)codeweavers.com>
Date: Mon Oct 12 17:20:57 2009 +0900
kernel32: Implement HeapQueryInformation, add some basic tests for it.
:040000 040000 65792138b4ecb4df0a323a534fd0e12d84379e80
91d5e4e851e21c3ca7b72663d6152d5b4b5ffbb3 M dlls
:040000 040000 2a67e12eca5063f497d228963956fcad7df7ebed
1a4a902ecba35e9b16486226ae060f2321f3c4e2 M include
--
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.
http://bugs.winehq.org/show_bug.cgi?id=4140
--- Comment #10 from Thomas Arendsen Hein <thomas(a)intevation.de> 2009-10-15 13:38:52 ---
(In reply to comment #9)
> Emu42 1.12 contains a workaround for this, see
> http://hp.giesselink.com/Emu42/CHANGES.TXT
>
> I verified this with wine 1.1.30 running emulations for HP42S and HP28S.
Regression:
When updating to wine 1.1.31, the problem occurs again!
(and downgrading to 1.1.30 fixes the problem again, no other changes)
I'm using the packages from "deb http://www.lamaresh.net/apt lenny main"
for amd64.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=6719
--- Comment #20 from Rosanne DiMesio <dimesio(a)earthlink.net> 2009-10-15 11:07:00 ---
Still present in 1.1.31.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=17573
Summary: Team Fortress 2 crashes on launch, with video mode
related errors. (1.1.16)
Product: Wine
Version: 1.1.16
Platform: PC-x86-64
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aoanla(a)yahoo.com
After upgrading from 1.1.15 to 1.1.16, I can no longer launch Team Fortress 2
from Steam.
Attempting to do so results in a brief splash of the intro video (literally a
fraction of a second) before the game crashes (but does not hang).
Wine outputs a ton of errors relating to not being able to find valid video
modes at around this time. I have attached a representative log of these,
starting from the first error that occurs on clicking "Launch Game", and
finishing when the game crashes.
It doesn't matter if I use -dxlevel 81 or -dxlevel 95 to choose different
DirectX rendering paths - all choices result in the same crash with the same
log.
This is with an nVidia 8800 GT, using nVidia driver release 180.35 on Ubuntu
8.10 x86_64. I can launch other native 3d games with this driver, and even
launch Bioshock in Wine 1.1.16 (from Steam) and begin a game in it.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=20373
Summary: Knights of the Old Republic II does not start
Product: Wine
Version: 1.1.31
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andy(a)wtribe.com
CC: andy(a)wtribe.com
Created an attachment (id=24142)
--> (http://bugs.winehq.org/attachment.cgi?id=24142)
dumps and backtrace following unhandled pagefault in `wine swkotor2.exe`
So, this one has me confused. I installed the game from the CDs, updated
through the patch at LucasArts, downloaded the no-cd for 1.0b, and running the
game lands me with an unhandled exception every time. I have disabled movies
and audio, changed the resolution in swkotor2.ini. I have tested this in
wine-1.1.29 through -1.1.31, and the 1.0.1 package in the jaunty repos. I
compiled 1.1.29-1.1.31 myself, and used the 1.1.31 package from the wine repo.
I have another computer that, using the exact same files, works fine. Both
computers are virtually identical LinuxMint 7 installs running wine-1.1.31.
Notable differences are that the comptuer that does not work is using TwinView
and Xinerama to get dual-monitor support through the nVidia drivers, and has a
Sound Blaster Audigy sound card, versus the onboard "HDA" audio on the other.
I've attached the base error. Let me know what else might be helpful, or what
else I can test.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=7929
--- Comment #88 from Damjan Jovanovic <damjan.jov(a)gmail.com> 2009-10-14 22:00:37 ---
(In reply to comment #87)
> (In reply to comment #86)
> > ...
> > I am eagerly awaiting progress on this new effort to bring network support.
> > ...
>
> For the curious, I'm researching the concern that Alexandre expressed (loss of
> packets in a multithreaded environment with simultaneous reads or selects on
> the same socket). In ws2_32 (normal operations) this is solved easily with a
> couple well-placed socket-specific spinlocks, within the Wine server (IOCP
> operation) it APPEARS that it is not necessary to do any locking since the IOCP
> polling and reading all seems to occur in the same thread (note that a socket
> can not be used "normally" once it has been flagged for IOCP). If anyone has
> any additional insight on this issue then I'd love to hear it, I'm a tad busy
> right now so tracking these things down in the server code is not on the top of
> my priority list.
>
While wineserver cannot AFAIK have a race condition with itself, maybe the
wineserver and a Windows app can race each other on the same socket even if
ws2_32 has its own internal spinlock?
APIs like DuplicateHandle() could also transfer the socket to another process,
which then uses its own ws2_32 critical section, so it seems like there could
be inter-process races too.
--
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.