Follow-up Comment #2, bug #11707 (project wesnoth):
This problem occurs for me too;
my configuration:
OS: OS X 10.5.2 apparently up to date as of the time of posting
Wesnoth: Wesnoth 1.4.2 from the DMG on the Wesnoth Website
Hardware: Intel Macbook Pro 17" high res latest generation (Feb 2008);
Further details available on request
Localisation: German OS X, Wenoth running in German.
While I am a software developer myself, I've only been using the mac for
about 3 weeks now, and thus don't yet have a full understanding of how I can
best generate useful reports when OS X detects a crash (I know how to get the
thing "Anonym" posted below, though).
I can compile from source with any settings you consider useful if that would
be helpful; pointers to what kind of things I should set in configure (or
whatever you use - never built wesnoth before, I will try later today)
welcome :)
I can't yet say with any certainty what is going wrong, but from the crashes
I've seen so far, my money would be on an audio-related problem (I currently
play with everything on, ie certainly music and SFX).
Aside: So far I've assumed that the "freeze" mentioned by the OP is actually
the delay between the program crashing, and OS X collecting data and/or
realizing the app is dead. I've had the crash both in full screen and
windowed mode, and certainly in windowed mode the rest of the OS continues on
trucking as if nothing was wrong during the "freeze".
Not reproducible (yet) for me though :(
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?11707>
_______________________________________________
Nachricht geschickt von/durch Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
