http://bugs.winehq.org/show_bug.cgi?id=23417
Summary: EverQuest II: Crashes immediately after hitting "Play" at character select screen Product: Wine Version: 1.2-rc5 Platform: x86 URL: http://www.everquest2.com/en/freeTrial.vm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: cww@denterprises.org
Selecting "Play" to enter the game from the character select screen in EQ2 crashes the game. It appears to be a null pointer reference. I am currently on my last few compiles of a git bisect, so I'll post more information soon-ish.
http://bugs.winehq.org/show_bug.cgi?id=23417
Colin Wetherbee cww@denterprises.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hverbeet@gmail.com
--- Comment #1 from Colin Wetherbee cww@denterprises.org 2010-06-28 04:50:37 --- The offending commit is the following.
9308c5499fa1f13ca5fff58f22a95ba60aa54726 is the first bad commit commit 9308c5499fa1f13ca5fff58f22a95ba60aa54726 Author: Henri Verbeet hverbeet@codeweavers.com Date: Thu Apr 22 18:55:58 2010 +0200
wined3d: Make sure all texture levels are allocated in surface_prepare_texture().
This fixes a regression introduced by commit af7dfcd378739127c50aa95ce40b13eb3d1950cf.
:040000 040000 68b150c5de10c7edc692a25afb9092a40b03f857 510a0ea7463d4031141b4510760aa491e882544b M dlls
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #2 from Henri Verbeet hverbeet@gmail.com 2010-06-28 07:34:48 --- what does the backtrace look like?
http://bugs.winehq.org/show_bug.cgi?id=23417
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression CC| |wylda@volny.cz
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #3 from Colin Wetherbee cww@denterprises.org 2010-06-28 18:13:23 --- (In reply to comment #2)
what does the backtrace look like?
I believe I'll have a chance to produce that tonight (USA time). I apologize for the delay.
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #4 from Colin Wetherbee cww@denterprises.org 2010-06-28 21:52:30 --- (In reply to comment #2)
what does the backtrace look like?
Here's the +d3d,+tid log.
http://www.colinwetherbee.com/data/wine-23417.bz2
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #5 from Henri Verbeet hverbeet@gmail.com 2010-06-29 05:03:47 --- That's missing the actual backtrace for some reason. If you can't get it to produce a proper backtrace, could you attach an "+d3d9,+ddraw,+tid,+seh,+d3d,+d3d_surface,+d3d_texture" log instead?
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #6 from Colin Wetherbee cww@denterprises.org 2010-07-03 18:49:10 --- (In reply to comment #5)
That's missing the actual backtrace for some reason. If you can't get it to produce a proper backtrace, could you attach an "+d3d9,+ddraw,+tid,+seh,+d3d,+d3d_surface,+d3d_texture" log instead?
Sure thing. The crash occurs on line 1,592,875.
http://www.colinwetherbee.com/data/wine-23417-alld3d.bz2
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #7 from Colin Wetherbee cww@denterprises.org 2010-07-03 18:51:04 --- (In reply to comment #6)
(In reply to comment #5)
That's missing the actual backtrace for some reason. If you can't get it to produce a proper backtrace, could you attach an "+d3d9,+ddraw,+tid,+seh,+d3d,+d3d_surface,+d3d_texture" log instead?
Sure thing. The crash occurs on line 1,592,875.
This new output is with wine-1.2-rc6, by the way. The previous log was with git set exactly to your commit.
http://bugs.winehq.org/show_bug.cgi?id=23417
John Beaulieu john.beaulieu@comcast.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #8 from John Beaulieu john.beaulieu@comcast.net 2010-07-04 12:02:12 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #9 from Henri Verbeet hverbeet@gmail.com 2010-07-07 16:25:07 --- Created an attachment (id=29430) --> (http://bugs.winehq.org/attachment.cgi?id=29430) patch
Does this patch work for you?
I also noticed the log and description look fairly similar to bug 19659, are you sure this isn't simply a duplicate?
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #10 from Colin Wetherbee cww@denterprises.org 2010-07-07 22:22:34 --- (In reply to comment #9)
Created an attachment (id=29430)
--> (http://bugs.winehq.org/attachment.cgi?id=29430) [details]
patch
Does this patch work for you?
Yes! It does! Thanks!
I also noticed the log and description look fairly similar to bug 19659, are you sure this isn't simply a duplicate?
I don't think it is, but I also think 19659 may have been fixed somewhere between then and now.
EQ2 has been fraught with problems running on Wine since 1.1.18, and they've been very difficult to track down.
http://bugs.winehq.org/show_bug.cgi?id=23417
Christofer Bergman morindhal@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |morindhal@gmail.com
--- Comment #11 from Christofer Bergman morindhal@gmail.com 2010-07-08 07:06:16 --- That's great news, any chance that this patch will make it into 1.2?
As mentioned the bug 19659 is related in the way that the EQ2 programmers used a similar way of memory management there but it's not the same place in the wine code and it's not triggered the same way. That bug is a crash from specific items that may or may not have been fixed since 1.1.18, there is no way to know without getting past this bug that prevents you to progress from the character select menu.
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #12 from Henri Verbeet hverbeet@gmail.com 2010-07-08 07:31:29 --- (In reply to comment #11)
That's great news, any chance that this patch will make it into 1.2?
I think it's safe enough, already submitted here: http://source.winehq.org/patches/data/63310
As mentioned the bug 19659 is related in the way that the EQ2 programmers used a similar way of memory management there but it's not the same place in the wine code and it's not triggered the same way. That bug is a crash from specific items that may or may not have been fixed since 1.1.18, there is no way to know without getting past this bug that prevents you to progress from the character select menu.
Bug 19659 probably got some issues mixed up, but e.g. the description and backtrace from comment 21 of that bug are pretty much identical to this one, and that clearly predates 9308c5499fa1f13ca5fff58f22a95ba60aa54726.
http://bugs.winehq.org/show_bug.cgi?id=23417
--- Comment #13 from Henri Verbeet hverbeet@gmail.com 2010-07-08 13:46:44 --- Should be fixed by 3ecaa4a41adc3f910792ace10bca59726c37ef69.
http://bugs.winehq.org/show_bug.cgi?id=23417
Colin Wetherbee cww@denterprises.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #14 from Colin Wetherbee cww@denterprises.org 2010-07-08 21:31:50 --- (In reply to comment #13)
Should be fixed by 3ecaa4a41adc3f910792ace10bca59726c37ef69.
Indeed, it is. The current git HEAD works very well.
Thanks again!
http://bugs.winehq.org/show_bug.cgi?id=23417
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Alexandre Julliard julliard@winehq.org 2010-07-09 11:57:32 --- Closing bugs fixed in 1.2-rc7.