The issue I was running into was definitely the bug you mentioned with the browser being open.
Testing on the ppc ibook 10.5 last night was good. I was able to download 5 files over a 1GB each with no crashes. It did pickup a show from sickbeard during the night, and crashed during the download, but not as I experienced before, I did not loose control of the pc and could terminate the hung sabnzbd process via activity monitor.\
I have set logs to debug and will share if I see it again.
I will test the intel mini running 10.6 tonight and update thread with results.
Help: Sabnzbd crashing on MAC 10.6.2 Snow Leopard
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Help: Sabnzbd crashing on MAC 10.6.2 Snow Leopard
I assume that so far you have been testing with the default "Plush" skin.
So assuming you narrow down the problem to having a web UI open,
you might check the other two skins.
There are two more, namely "smpl" and "Classic".
The "smpl" looks quite different and is very different internally.
"Classic" is very down-to-earth using as simple as possible HTML code.
However "Classic" is not recommended with large queues and histories (no pagination).
Both are a bit behind on features.
So assuming you narrow down the problem to having a web UI open,
you might check the other two skins.
There are two more, namely "smpl" and "Classic".
The "smpl" looks quite different and is very different internally.
"Classic" is very down-to-earth using as simple as possible HTML code.
However "Classic" is not recommended with large queues and histories (no pagination).
Both are a bit behind on features.