I don't see much in the Event Viewer and nothing that appears at the
times it breaks. I have seen this, which may be related:
Event Type: Error
Event Source: Application
Event Category: None
Event ID: 0
Date: 6/12/2005
Time: 8:59:19 PM
User: N/A
Computer:
I have been having more general problems with the nightlies from the
last week, all fairly consistent. Platform: W2K Pro. Running as a
service. SB2, wired. Last nightly used was 6/11
- Slimserver basically just dies. Under Services and from the Task
Manager it appears to be running - but
On Jun 12, 2005, at 4:47 AM, Charles Stanton wrote:
I have been having more general problems with the nightlies from the
last week, all fairly consistent. Platform: W2K Pro. Running as a
service. SB2, wired. Last nightly used was 6/11
- Slimserver basically just dies. Under Services and
Hi,
6.1, 6/11 nightly
I still have the problem: the web interface never stops loading, and
some images never get drawn in. It never stops working completely
though.
Edit: Should say this is with FF, and I'm running slimserver on linux.
The interface seems to work fine in IE.
--
beo
* beo shaped the electrons to say...
6.1, 6/11 nightly
I still have the problem: the web interface never stops loading, and
some images never get drawn in. It never stops working completely
though.
Edit: Should say this is with FF, and I'm running slimserver on linux.
The interface seems to
Thanks for the awesome turn around.
When I run --d_http and use FF 1.0.3, I see the output below, and then
it just sits there not doing anything...
2005-06-11 15:41:13.1881 More to send to 10.0.0.100
2005-06-11 15:41:13.1889 No more messages to send to 10.0.0.100
2005-06-11 15:41:13.1898 More
* beo shaped the electrons to say...
When I run --d_http and use FF 1.0.3, I see the output below, and then
it just sits there not doing anything...
2005-06-11 15:41:13.1881 More to send to 10.0.0.100
2005-06-11 15:41:13.1889 No more messages to send to 10.0.0.100
2005-06-11 15:41:13.1898 More
Changing network.http.keep-alive to false fixes it. I'm not sure how
to tell/where to look to try and debug where the session is hanginging.
It does work fine in 6.0.x.
I was going to see if a different skin fixed it, but every time I
changed from default it crashed -- a 6.1 quirk?
--
beo
