Project

General

Profile

Actions

Emulator Issues #8377

closed

[Wii] RZJE69 - Dead Space: Extraction. Unknown Pointer message and crash

Added by valsnegro about 10 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?
Dead Space: Extraction

Game ID?
RZJE69

What's the problem? Describe what went wrong in few words.
The emulator throws several messages like the following:
Unknown Pointer 0x1e6ecdae PC 0x80167 ddc LR 0x80166828

The messages can be skipped by keeping escape pressed, but the only time I kept on playing, Dolphin crashed a few minutes later in the same chapter. I haven't had the heart to recheck. I don't know if both issues are related.

What did you expect to happen instead?
Not receiving any error message at all.

What steps will reproduce the problem?

  1. Start chapter 2
  2. Let the load screen run its course
  3. You should be receiving messages already before any 3D graphics appear.

Which versions of Dolphin did you test on?
master-4.0-5809-x64 and master-4.0-5845-x64

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Yes. I tried 4.0.2 and it does not happen. I also tried several later releases at random and the latest I tried, master-4.0-5143-x64 did not have this issue either.

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Win7 x64
Intel Core 2 Quad Q9450
4 GB DDR2
Nvidia GeForce GTX 560 Ti

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Not at this moment

Actions #1

Updated by JMC4789 about 10 years ago

Try to narrow it down to the exact build where behavior changed with bisecting so I can assign an owner. Thanks!

Actions #2

Updated by valsnegro about 10 years ago

Alright, the problem appears between 4.0-5445-x64, where it does not happen, and 4.0-5450-x64 the first instance where it happens.

Actions #3

Updated by magumagu9 about 10 years ago

That's me, but I don't have the game. Can someone get a stack trace?

Actions #4

Updated by seapancake about 10 years ago

I have tested this bug and can replicate it infrequently in 5460 however a bug with mouse accuracy prevented me from doing much testing, also seeing it in 5862.

Chapter loads and then the following series of errors are seen.

http://i.imgur.com/pUJWYsL.png
http://i.imgur.com/ZS2rpBa.png
http://i.imgur.com/UcaiaVm.png

Frames progress if you hit ok on the errors and eventually after about 30 errors they stop appearing and the chapter plays normally, see below.

http://i.imgur.com/mm1pwvj.png

I enabled logging in Dolphin but apart from that I have no idea how to get a stack trace, if someone can enlighten me (I tried searching) I'm happy to get that as well.

Running Windows 8.1.

Actions #5

Updated by magumagu9 about 10 years ago

More specifically, I'm looking for a developer who knows how to use a debugger to get a stack trace for the call to Memory::GetPointer(). The value 0x1e6ecdae is suspicious.

Actions #6

Updated by valsnegro about 10 years ago

In regards to the crash I suffered, I tried again and it happened again at the same spot while playing in OpenGL with internal resolution 2x, PPL, anisotropic 8x and v-sync. The rest as default.

Here is the first couple of crash windoIn regards to the crash I suffered, I tried again and it happened again at the same spot while playing in OpenGL with internal resolution 2x, PPL, anisotropic 8x and v-sync. The rest as default.

Here is the first couple of crash windows:
http://i.imgur.com/P5dcVe8.jpg
http://i.imgur.com/DOPEEDb.jpg

I then changed to internal resolution 1x and v-sync only and tried again. The crash did not occur.

EDIT: I've checked out a couple of videos on Youtube and it seems it doesn't happen to everyone. I'll ask in the forum to see if anyone else can reproduce it.

Actions #7

Updated by JMC4789 almost 10 years ago

Is this fixed in latest master? We made a change that killed some unknown pointer errors.

Actions #8

Updated by seapancake almost 10 years ago

I can confirm this is no longer an issue in 6734, can start chapter 2 without any errors where I used to get the above.

Actions #9

Updated by JMC4789 almost 10 years ago

  • Status changed from New to Fixed
Actions

Also available in: Atom PDF