Bug 204229 - emulators/wine-devel Crash in winecfg
Summary: emulators/wine-devel Crash in winecfg
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Gerald Pfeifer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-02 19:04 UTC by Ivan
Modified: 2018-01-17 11:14 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan 2015-11-02 19:04:19 UTC
Steps to reproduce:

1. Have OSS devices
2. Make 64-bit wine prefix
3. Start winecfg in 64-bit prefix
4. Click on the audio tab

Wine configuration tool hangs immediatly with Unhandled stack overflow at address 0x7bc53842 (thread 0039), starting debugger...

Switching off OSS support in wine prefix registry seems to solve the issue, but this is hardly a proper solution.
Comment 1 Ivan 2015-11-02 19:06:03 UTC
Not a 1.7.54 regression, the same thing is 1.7.54. And, actually my test games hangs with the same stack overflow error (with or without OSS support). If problem with winecfg will be confirmed, maybe this is the post easy test subject to find the roots of stack corruption.
Comment 2 Gerald Pfeifer freebsd_committer freebsd_triage 2015-11-02 23:04:59 UTC
David, is this something you'd be able to have a look at?  (I won't,
so if you aren't, either, we'll have to assign this to ports@.)
Comment 3 Ivan 2015-11-03 09:54:34 UTC
Can you at least reproduce the issue on your system? If yes, we could bump importance and file PR on upstream.
Comment 4 David Naylor freebsd_committer freebsd_triage 2015-12-09 07:07:32 UTC
I will have a took at this - I think we might be missing a patch or two that hasn't been upstreamed as yet.
Comment 5 David Naylor freebsd_committer freebsd_triage 2016-01-17 18:17:09 UTC
I can confirm this stack overflow error with wine-devel with all uncommitted patches (and with stock wine).  Please report this issue upstream (including myself and gerald as CC).  (I will close this report when the issue is reported upstream.)
Comment 6 Gerald Pfeifer freebsd_committer freebsd_triage 2016-05-22 13:40:27 UTC
*** Bug 209688 has been marked as a duplicate of this bug. ***
Comment 7 Walter Schwarzenfeld 2018-01-17 09:33:06 UTC
Is this still relevant?
Comment 8 Gerald Pfeifer freebsd_committer freebsd_triage 2018-01-17 11:11:25 UTC
Not sure why you reassigned this to me now W., but looking at the
connected bug reports it appears we can close this one as fixed?
Comment 9 Walter Schwarzenfeld 2018-01-17 11:14:19 UTC
Sorry, was a mistake with the name.