Bugzilla – Bug 4134
6.5b3 web interface crashes Safari 1.3.2
Last modified: 2011-03-16 04:18:42 UTC
With the interface skin set to default, and with the SlimServer interface just operating normally, Safari regularly dies. This didn't happen with the previous versions of SlimServer such as 6.3.1 I will attach the crash report from the most recent Safari death. It looks like something choked during an xml parse. Repeat by: Connect to the SlimServer v6.5b3 via the default web address on a System 10.3.9 mac using Safari 1.3.2. Wait. Eventually, usually within a few minutes to half an hour, BOOM Safari crashes.
Created attachment 1549 [details] Paste-in of crash report text from Safari crash.
I guess there's no way to upgrade to Safari 2.0.4 unless you also upgrade to Tiger? I'll use 2.0.4 for a while and see if it crashes.
Been running 2 tabs on 2 different SlimServer instances for over an hour and have yet to see a crash.
Firefox doesn't crash either. It looks like an Apple bug. :-( I suppose we could say that the 6.5 web interface requires Safari 2.0 or later. Unfortunately Safari 1.3 will be with us for a while still. And Apple will say anything under 10.3.9 isn't worth working on with 10.5 coming out. Sigh.
I was unable to reproduce the crash under 10.3.9 myself. Perhaps the XMLHttpRequest part is coincidental. Please report asome of the other crash dumps just to see if there is something consistent.
I don't suppose the "light" skin works any better? :)
Chris to try to reproduce on his 10.3.9 machine.
Is the right hand pane, that normally shows what the clients are doing supposed to be blank with the Light skin? I connected to the server, switched to the Light skin. The left frame refreshed, but the right did not. I hit reload, and the right frame went blank. I hit <shift>reload and got 3 columns. The left column as expected, Instead of the client column, the right column duplicated the server column and added the client column. It does that every time I do <shift>reload. Should I open another bug? Man! Is it hard to get rid of that middle column. I switched back to default, and had to hit <shift>reload to get the basic interface there, but there's still a small frame with a scroll bar just above the playlist that WANTS to be the server interface home page. Let's restart Safari...
I restarted Safari and now the default interface stays up for a long time without crashing. Glorious... A heisenbug, just what we all need. :-( (It really DID crash multiple times yesterday.) I shall leave the interface running while I go meet some people for dinner and see if I come back to an interface or a crash dump.
One more theory: Maybe you have to have two client devices active for the crash to happen?
I got Safari to crash again, but not reliably. It MIGHT be related to sketchy code in managing the list of clients served. I switched the names of my two linked clients from: "Work Room", "SoundBridge" to: "Work Room Longname", "SoundBridge Longname". After a redisplay of the song queue redrew the pull-down menu, I pulled it down and, BOOM! But alas, restarting Safari with the long-named systems has not yet resulted in another crash. At any rate, I shall attach a second crash dump. I notice that this one isn't in the XML parsing. :-( It appears to be in the event dispatcher. Sigh and double sigh!
Created attachment 1556 [details] crash dump from safari
my setup: Safari 1.3.2 (v312.6), open on Default skin Firefox 1.5.0.7 open on Fishbone skin 1 Slimp3 1 Squeezebox G 1 transporter 2 SB2 1 SB3 server version 7.0a1 and 6.5 throughout the evening. cannot reproduce the crash. I have a hard time thinking it would be the particular cient, so I'm wondering if ram might be suspect here.
Created attachment 1605 [details] Yet another Safari Crash Dump. Here's another crash dump, recognizing that it might still not be useful...
I wasn't able to reproduce this for a fix in 6.5.1. Setting it to 7.0 and will look at it some more.
Steven to check to see if this is important and still reproducible.
Chris, once we have that PowerPC Mac I will take a look. Safari 1.3.2 requires 10.3.9 and our Intel Macs wont run it.
is this the same as bug 6009?
No, its not the same as bug 6009 since this is the old default skin now called classic in SC 7. I have not been able to reproduce either. This may be a moot point since the new default skin in SC 7 is not supported in Safari 1.3.2. William do you still see this issue?
Thanks very much for continuing to watch this issue. I too am unable to reproduce this problem. Perhaps it was something in MacOS 10.3.9. Perhaps Safari 1.3.2. Perhaps 6.5b3 of SlimServer. Last night I started up the Classic interface on my current Mac Safari Setup which is Safari 2.0.4 on MacOS 10.4.10, with one of the nightly builds of Slim Server 7.0a. I let it run all night, and it didn't crash Safari. I'd say let's close this saying, "Worksforme", with the comment that it does not seem to happen to the original reporting person when running more modern versions of everything. -Bill Cattey
Thanks for the feedback Bill, it is really appreciated! Resolving as works for me.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.