anroine347 / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

Segmentation fault using Glide64mk2 in LOZ:MM and the Debug Master Quest [f2] + Pause Crashing #551

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Describe your system:
 - Ubuntu 12.04 (64-bit):
 - 64-bit AMD Athlon 64x2:
 - Mupen64Plus version: Latest source compiled with default values
 - Plugins used:Glide64mk2

For visual artifacts, give:
 - game name and CRC/MD5 hash:

1)
Goodname: Legend of Zelda, The - Majora's Mask (U) [!]
Core: Name: ZELDA MAJORA'S MASK 
Core: MD5: 2A0A8ACB61538235BC1094D297FB6556
Core: CRC: 5354631c 3a2def0
Core: Imagetype: .z64 (native)
Core: Rom size: 33554432 bytes (or 32 Mb or 256 Megabits)
Core: Version: 144b
Core: Manufacturer: Nintendo
Core: Country: USA

2)
Goodname: Legend of Zelda, The - Ocarina of Time - Master Quest (U) (Debug 
Version)
Core: Name: THE LEGEND OF ZELDA 
Core: MD5: 110523A9595CA9DEC61402E628878C84
Core: CRC: 917d18f6 69bc5453
Core: Imagetype: .z64 (native)
Core: Rom size: 67108864 bytes (or 64 Mb or 512 Megabits)
Core: Version: 144c
Core: Manufacturer: Nintendo
Core: Country: USA

Describe the problem:

1) In Majora's Mask, Mupen64plus crashes with a segmentation fault error 
message as approaching the old Granny's room into the Stock Pot Inn.

2) In LOZ: OOT - Master Quest, Mupen64plus crashes with a segmentation fault as 
blowing the inner wall at the beginning of Dodongo's Cavern. Also, the game is 
very prone to crashing as trying to open the pause subscreens.

Please provide any additional information below.

Attaching the states to load in order to verify the issue.

Original issue reported on code.google.com by alessand...@gmail.com on 1 Jun 2013 at 1:05

Attachments:

GoogleCodeExporter commented 8 years ago
I've just tried it with the build from 
https://launchpad.net/~sven-eckelmann/+archive/ppa-mupen64plus

1) the room you've mentioned it the one on the first floor (down the chairs), 
then 2x left and then the first one on the right. Here it didn't crash. when I 
entered the room with the granny in the chair.

Did you had some special configuration or some texture packs?

2) I couldn't fine a ROM with this md5. Are you sure it is a good rom? The one 
i know as good dump of the Debug version has the md5 
8CA71E87DE4CE5E9F6EC916202A623E9

Could you please try the builds from the ppa (please check that you don't 
accidentally use the plugins or the core from your other installation; give the 
full path to --gfx, --audio, --input, --corelib, --rsp -- or verify with strace 
that the correct ones are used -- the right ones are in 
/usr/lib/x86_64-linux-gnu/mupen64plus/ and use the core lib 
/usr/lib/x86_64-linux-gnu/libmupen64plus.so.2.0.0 )

Original comment by s...@narfation.org on 6 Jun 2013 at 6:44

GoogleCodeExporter commented 8 years ago
Thanks for replying! First things first, I have no mupen64plus directory under 
x86_64-linux-gnu. All plugins and stuff are located in 
/usr/local/lib/mupen64plus/. The strange thing is that whenever I change the 
video plugin in the config file to something different from Rice, mupen64plus 
automatically loads glide64mk2....quite odd.

I am using textures packs under Rice, but I did not set glide64mk2 any 
differently from how it comes from the source so it does not actually use them. 
Checked the Majora's Mask thing once again and I'm almost sure it just crashes 
after a few seconds, the game doesn't really care if I approach that room or 
not...I compiled from Hg following the wiki page of this project.

 Special configurations: I had set the ScreenUpdateSetting to 2 in order to solve the flickering of the pause screen in OOT and MM. I'm seriously thinking my glide64mk2 plugin is corrupted. I expect it to have the same md5 of yours if we're running under the same kernel, what's yours? Mine is ae0679f154a6d5d5d3655afe84d34e84

As of the debug rom, I don't really know. What I know is that the Giant knife 
to biggoron sword code provided by Zeth worked, but since that is about RAM 
addresses I guess even a corrupted dump could do the job...

Original comment by alessand...@gmail.com on 6 Jun 2013 at 10:02

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Ok, installed the ppa version and glide64mk2. Now, it is no longer crashing. 
Instead of crashing, graphics layers get lost into nothingness. This is what 
really happens, in the other version I had the results were a plain crash but 
here comes the true stuff. The flashing heart and the clock don't show just 
like in Rice, but as you can see lots of stuff is missing!

Original comment by alessand...@gmail.com on 6 Jun 2013 at 11:06

Attachments:

GoogleCodeExporter commented 8 years ago
Ok, installed the ppa version and glide64mk2. Now, it is no longer crashing. 
Instead of crashing, graphics layers get lost into nothingness. This is what 
really happens, in the other version I had the results were a plain crash but 
here comes the true stuff. The flashing heart and the clock don't show just 
like in Rice, but as you can see lots of stuff is missing!

Original comment by alessand...@gmail.com on 6 Jun 2013 at 11:06

Attachments:

GoogleCodeExporter commented 8 years ago
Can you please provide a savestate near the problematic situation were the 
missing world/objects problem happens.

The md5 sum of the glide64mk2 doesn't really depend on the kernel it is running 
on. It depends on the compiler, the compiler flags, the used external resources 
(static libs, headers, ...) and the actual source code. But you can find the 
hash sum of the plugin inside the deb. And it will also be installed in 
/var/lib/dpkg/info/mupen64plus-video-glide64mk2:amd64.md5sums -- this file 
tells me that I would expect the md5sum (only the .so) 
712556283754e4819eee3a90a3a29af4 for the Ubuntu 12.04 build of 
mupen64plus-video-glide64mk2 version 2.0~rc2.

ScreenUpdateSetting is a Rice setting and has nothing to do with Glide64Mk2.

Please don't use cheats when reporting bugs. When you've used one, please 
disable cheats, reset the game and only use a savegame (not a savestate) to go 
back to the problematic area (aka. load ingame and go to the area which 
triggered the problem).

Why do you say "ppa version _AND_ glide64mk2". You should have used the 
glide64mk2 from the  ppa for this test and not your self compiled one.

Original comment by s...@narfation.org on 7 Jun 2013 at 7:17

GoogleCodeExporter commented 8 years ago
Attached. Sorry, I said ppa version and glide64mk2 because it didn't install 
immediately among the core library, nothing really important. The md5 matches.

I'll try to describe the best way I can what happens and where: from that very 
position, pressing Z to move the camera is enough to cause the issue. Also, 
entering the old granny's room causes the issue. Exiting the stock pot inn and 
entering back from the main entrance causes the issue aswell.

 Once the issue is triggered, pausing and unpausing solves it. If you try to reproduce any of the three things after they have already happened in a game session, they won't happen. Reloading the save state and trying again to trigger the issue does not work, you have to quit mupen64plus in order to reproduce again. No cheats have been loaded.

The same instance happens in the other savestate, the one of the OOT debug ROM. 
The different md5sum there was because of a patch I was using.

Original comment by alessand...@gmail.com on 9 Jun 2013 at 2:04

Attachments:

GoogleCodeExporter commented 8 years ago
I have real big problems to recreate the problem. Sorry

Maybe someone else here can check it out.

Original comment by s...@narfation.org on 14 Jun 2013 at 2:11

GoogleCodeExporter commented 8 years ago
I will wipe out my drive and try with a fresh new install of the OS, maybe it 
is some strange installation issue with my machine. At this point I'm fairly 
convinced this is my issue and mine alone.

Original comment by alessand...@gmail.com on 15 Jun 2013 at 12:45

GoogleCodeExporter commented 8 years ago
This could also be graphics driver related

Original comment by s...@narfation.org on 15 Jun 2013 at 5:25

GoogleCodeExporter commented 8 years ago
The Majora's Mask crash is easily reproducible by starting the game and letting 
the demo play out. Just after the camera pans past Anju in the inn, mupen 
crashes.

Windows 7, Radeon HD 6850, most recent versions of everything. Default 
settings. CRC matches the OP's.

Occurs on Glide64mk2 but not Rice. It'd be preferable to use Glide for this 
game because it handles everything else beautifully.

Original comment by CloningDonor on 10 Sep 2013 at 7:22

GoogleCodeExporter commented 8 years ago
to clarify, "most recent version" as in whatever the latest binary release is 
(2.0, july 4) because screw compiling things on Windows.

on that note, I compiled the Mercurial version on Ubuntu and it works fine, so 
this issue may be already fixed. I might test some more later.

Original comment by CloningDonor on 13 Sep 2013 at 10:01

GoogleCodeExporter commented 8 years ago
Please test the mxe builds on windows when you want to *really* test the newest 
version on windows. https://bitbucket.org/ecsv/mupen64plus-mxe-daily

Original comment by s...@narfation.org on 13 Sep 2013 at 10:07

GoogleCodeExporter commented 8 years ago
Sorry, I should've been more clear to begin with.

It works. I guess this issue can be closed so long as the OP doesn't object. 
Hope to see a release soon.

Original comment by CloningDonor on 14 Sep 2013 at 7:26

GoogleCodeExporter commented 8 years ago
Just rebuilt mupen64plus on Debian 7 (latest from mercurial repo). The issue 
persists. But since not a person managed to reproduce it I may conclude that's 
my GPU's issue. It's just very strange though...

Original comment by alessand...@gmail.com on 18 Sep 2013 at 4:25