"Cannot Load Address"

[Matt Rehder]

When I see this happen, often the CSS for a page will fail to load.  
Then when I try to go to a different page or refresh I get the blank 
page with the error message and it's quit OW time.

-matt

On Apr 12, 2004, at 12:14 PM, Brendan Sweeney wrote:

> I get it on my power book g4 all the time.  Also seems to be related 
> to run time, although not an 'iff on for x hours' kind of thing.  But 
> definitely more likely to happen at any one time when it's been 
> running for an extended period.
>
> And it's not always just the top level page that gets the error, 
> sometimes I'll load a page and it will start to layout and then 90% of 
> the images will get the failure icon.  Now I usually recognize that 
> for what it is and just quit, but the first couple times I went "hun, 
> that's odd" and tried to load something else, where I'd get the 'nil 
> value' bug.  I don't need to force quit when that happens though.
>
> ~BS
> On Apr 12, 2004, at 10:49 AM, Matt Rehder wrote:
>
>> I get this error after about 18 hours of OW running on my dual 500 
>> G4.  It's happened since webcore was added to OW 4, and has happened 
>> with every beta.  I don't even need to use OW.  Start it in the 
>> morning, don't load a single page and come back about a day later and 
>> it will throw the below error and I'll need to force quit.
>>
>> I have a powerbook G4 and I've only gotten this error once with OW, 
>> so this is related to the hardware somehow.  It is easily the most 
>> annoying OW bug for me.  If there is any data I can provide, please 
>> let me know.
>>
>> -matt
>>
>> On Apr 10, 2004, at 6:34 AM, Eugene Lee wrote:
>>
>>> If I can run OW long enough while not crashing, eventually it reaches
>>> a state where it can no longer load web pages.  It displays this 
>>> error
>>> message in the browser window:
>>>
>>> 	Cannot Load Address
>>> 	*** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value
>>>
>>> I've come across this exact error message with all (up to current 
>>> Beta 5
>>> build v549) versions of OW 5.0, and even with version 4.5.  There's 
>>> no
>>> quick way to trigger this error.  But when OW reaches this state, is
>>> there anything I can do to provide more bug reporting info?
>>>
>>>
>>> -- 
>>> Eugene Lee
>>> http://www.coxar.pwp.blueyonder.co.uk/
>>> _______________________________________________
>>> OmniWeb-l mailing list
>>> OmniWeb-l at omnigroup.com
>>> http://www.omnigroup.com/mailman/listinfo/omniweb-l
>>>
>>
>> _______________________________________________
>> OmniWeb-l mailing list
>> OmniWeb-l at omnigroup.com
>> http://www.omnigroup.com/mailman/listinfo/omniweb-l
>>
>>
> http://www.thewonderllama.com
>
>