Page 1 of 1

Star Browser sometimes crashes Celestia v1.3.1-1

Posted: 22.01.2004, 02:11
by selden
Various legal uses of the Star Browser sometimes cause Celestia to crash. It isn't entirely reproducable. I think it may have to do with how much of Celestia's window is covered by the menu.

1. Goto a location in space

Code: Select all

OpenCluster "LNRW" {
RA 12.85833
Dec 7.128334
Distance 201
Radius 0.
1
}


Open the StarBrowser menu
Type a number (e.g. 20) into the "Maximum stars in list" field
Type "return"
Exception: 0xc0000005 flags: 0
record: 0 Address: 000...0004135d6

It's done this 4 out of 5 times.

2. It also crashed once when I selected a star in the browser menu.
Now it won't. *sigh*

The system hasn't been reporting any disk (SCSI) or memory (ECC) errors, so I don't think it's a hardware problem.

System:
256MB 500MHz P3, WinXP Pro SP1
128MB Ti4200, Nvidia drivers v44.03

Re: Star Browser sometimes crashes Celestia v1.3.1-1

Posted: 23.01.2004, 07:36
by don
selden wrote:1. Goto a location in space

Code: Select all

OpenCluster "LNRW" {
RA 12.85833
Dec 7.128334
Distance 201
Radius 0.
1
}
How does one "go to" this location?

If I go anywhere in space (another star, a moon, etc.) I am not able to duplicate this error.


selden wrote:I think it may have to do with how much of Celestia's window is covered by the menu.

I also tried it with many different Celestia window sizes, with no crash.

What display option do you select, the default (Nearest)? Do you click on any of the buttons or just press the Enter key.

Thanks for any more info you can provide.

Cheers,

-Don G.

Re: Star Browser sometimes crashes Celestia v1.3.1-1

Posted: 23.01.2004, 10:49
by selden
don wrote:
selden wrote:1. Goto a location in space

Code: Select all

OpenCluster "LNRW" {
RA 12.85833
Dec 7.128334
Distance 201
Radius 0.
1
}
How does one "go to" this location?

create a DSC file in your extras (or Addons) directory containing the code listed above.
Then start Celestia and type

[return]
LNRW[return]

(where [return] stands for the carriage-return or Enter key)

Although it turns out that the GoTo LNRW is unnecessary. See below.

If I go anywhere in space (another star, a moon, etc.) I am not able to duplicate this error.

It also crashes for me with no addons:

Remove all Addons from Celestia's extras folder.

start Celestia v1.3.1-1
resize the desktop window so it's smaller than the star browser menu window
exit Celestia
start Celestia
wait for Io to stop moving in the window
open Star-Browser
highlight 100
type in the value
20 [return]
*crash* -- sometimes--

It crashed several times
then I started Celestia and resized the window larger (no crash)
exited and started Celestia,
resized the window smaller than the StarBrowser menu
(no crash)
exited and started Celestia,
no window size change
(no crash)
exited and started Celestia,
no window size change
*crash*

and now it crashes every time (without a window resize)

selden wrote:I think it may have to do with how much of Celestia's window is covered by the menu.
I also tried it with many different Celestia window sizes, with no crash.

What display option do you select, the default (Nearest)? [/quote] I don't touch any of the options when trying to reproduce the problem. I am careful to do *nothing* but start Celestia, wait for motion to stop, open StarBrowser, hightlight field, 20[return]
*crash*

Do you click on any of the buttons or just press the Enter key.

I only highlight and change the entry in the "Maximum Stars Displayed in List" field, then press [return]. I have
not been using the numeric pad [enter] key.

The fact that it's inconsistant (it didn't crash the most recent time I tried) suggests that it may depend on something that Celestia does which varies from one second to the next.

Posted: 23.01.2004, 16:58
by chris
I've reproduced the problem in a debug version of Celestia and am working on tracking down the cause. Thanks for the bug report Selden.

--Chris

Posted: 23.01.2004, 20:39
by don
Thank you for the detailed steps Selden. :)

Posted: 26.01.2004, 17:10
by chris
I checked the fix for this problem into CVS.

--Chris

Posted: 26.01.2004, 17:19
by selden
Chris,

Thanks!