http://bugs.winehq.org/show_bug.cgi?id=6597
Summary: Shockwave custom MoveCursor component unhandled page
fault
Product: Wine
Version: 0.9.24.
Platform: Other
URL: http://necromanthus.com/Games/ShockWave/quake3.html
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ploujj(a)gmail.com
I used wine 258008012cbd2aebf96da5d6f830069725c08b82 from git
Installed Firefox 2 in a brand new ~/.wine
Installed adobe Shockwave
Navigated to the given URL
Agreed to install a required third party shockwave component:
- Shockwave component MoveCursor.w32 sn: 014182deb3d9977a86418a2f539ac9a1
clicked "Play" in the shockwave player area
1 second later Firefox crashed with the following output
Should there be an appdb entry for this shockwave component or can this be
counted under "Shockwave"?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6126
------- Additional Comments From jkohen(a)users.sourceforge.net 2006-03-11 08:23 -------
This bug is still present in Wine 0.9.24. Is it customary to bump the version
number in the report?
To the author of the original patch: this is preventing me from upgrading wine
for 7 versions already. If there is anything I can do to help you work on a fix,
please let me know.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6594
------- Additional Comments From dank(a)kegel.com 2006-03-11 08:16 -------
Wine should probably come up with a fix that doesn't
require this workaround, but:
The appdb entry for call of duty 1.5 mentions
that umount -l can be used to force the
cdrom to be unmounted even though something's
still open on it:
http://appdb.winehq.org/commentview.php?iAppId=1346&iVersionId=3603&iThread…
(The question is, can this workaround be made
easy for users. That's probably a Linux distribution
quality-of-implementation issue.)
The guy who mentioned this even wrote a Loki
installer script to get Call of Duty to
install under Wine. Woot...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6505
------- Additional Comments From atrauzzi(a)gmail.com 2006-03-11 08:15 -------
Another hang while riding from Crossroads to Ogrimmar. Still outdoors, early in
the trip.
wine: Unhandled page fault on write access to 0x4a837ba8 at address 0x7bc35be4
(thread 0009), starting debugger...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6578
------- Additional Comments From purple_skunk(a)msn.com 2006-03-11 08:07 -------
Confirming that the bug is now gone in wine CVS, thanks to Jacek Caban who
reverted his changes.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6505
------- Additional Comments From atrauzzi(a)gmail.com 2006-03-11 07:33 -------
Also, don't tell me that:
"err:seh:setup_exception stack overflow 288 bytes in thread 0009 eip 00742bae
esp 00230ee0 stack 0x231000-0x340000"
Isn't worth noting. Have you even looked at my logs? Or do you see the first
few lines of "fixmes" and go "OMGOMGOMGOMG SOMEONE POSTING FIXMES OMG HE KNOWS
NOTHING".
Ever thought that I'm including the last few lines to ensure that if it does end
up being important, that the information is there?
The last log I posted is a whopping THREE LINES short and contains not a single
fixme. It contains an error that is printed to my console -- wait for it --
WHEN THE GAME CRASHES!
(And of course, you already know by now that adding extra debug information
slows the game down enough to prevent this bug from happening, don't you?
Please? I mean, I've only said it at least three times now.)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6505
atrauzzi(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |major
------- Additional Comments From atrauzzi(a)gmail.com 2006-03-11 07:27 -------
The "debug channels" prevent the bug from happening.
Why do you refuse to acknowledge this?
I've been submitting bugs for more than four years and I know for a fact that
everything I say gets ignored in an attempt to de-prioritize my submission.
So here we are with a new account of this bug. It is present on THREE
architecturally different machines of mine. (Tested on laptop, problem exists
there as well).
I've given all that I can about the problem. It seems to be related to large
areas. Cities, outdoors. Anything that causes rather chaotic loading of
information from the HDD to draw in horizons.
So, just in case you're one of the simpletons who only replies to the last
paragraph of a message: Increasing log output and sustaining a drop in speed
prevents the bug from occuring.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6590
------- Additional Comments From kkelly(a)cinci.rr.com 2006-03-11 07:20 -------
That configure command did the trick. I'll run a regression test and post the
results.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.