Mupen crashes on launch

[GoogleCodeExporter]

Describe your system:
 - Linux distribution: Fedora 9
 - Machine type: 32-bit
 - Mupen64Plus version: 1.5
 - Plugins used: (defaults) Rice Video 1.5, jttL's SDL audio 1.5, blight's
SDL input 0.0.10, hacktarux/azimer hle rsp

Describe the problem: Program crashes when started.

Please provide any additional information below.
Installed and worked without a problem initially, then after tweaking
graphics settings a few times and adding a directory to the rom browser,
mupen began crashing immediately every time I launched it. When launched
from a terminal I recieve the line: 
Bad address
2d031478-ea71-67f7-5fe95d98-4b057ad4 is dumped
I've attempted to reset everything back to default, including removing the
rom directory, but it's made no difference. Every time I receive a crash
message with an accompanying bug report, which I've attached.

Original issue reported on code.google.com by allnutt....@gmail.com on 18 Feb 2009 at 3:53

Attachments:

• mupen64plus-bugreport.txt

[GoogleCodeExporter]

Since you say that you have been tweaking graphics setting, I'm thinking maybe a
configuration file has become corrupted.

If you cheack the  ~/.mupen64plus directory, there are some config files. Try to
rename the various config files, and they should be regenerated.

If this is the problem, maybe you can post the config file that is causing 
problems,
and maybe even how to reproduce it.

Original comment by olejl77@gmail.com on 18 Feb 2009 at 7:42

[GoogleCodeExporter]

Thanks, I narrowed it down to the rombrowser.cache file in the ~/.mupen64plus
directory. I can't view the file, so it's hard for me to say what's wrong with 
it,
but removing the file fixed the problem. I was also able to recreate the crash, 
but
it only seems to happen under very specific conditions. By adding a folder to 
the rom
browser directories list that contained a large number of incomplete/corrupted 
roms,
then removing the directory from mupen's directory list before it finished 
loading
all the roms to the browser, it would cause mupen64plus to crash the next time 
it was
opened. If mupen finished loading the roms before the directory was removed, 
there
was no problem. I don't have a large folder of good roms to test this on, so 
I'm not
sure if it's just with bad roms, or if it's a problem with the caching not 
dumping
removed files properly. I'll attach a copy of the bad rombrowser.cache file for
reference. Thanks for the help

Original comment by allnutt....@gmail.com on 18 Feb 2009 at 8:41

Attachments:

• rombrowser.cache

[GoogleCodeExporter]

The ROM browser has been removed and is no longer being maintained in the core
Mupen64Plus project.  This code may be pulled in to a future GUI front-end for
Mupen64Plus 2.0, and if this bug still persists then it should be filed with 
the GUI
project.

Original comment by richard...@gmail.com on 12 Jan 2010 at 5:55

• Changed state: WontFix