On Wed, Aug 12, 2009 at 11:45:27PM +0000, corvid wrote:
Jorge wrote:
On Fri, Aug 07, 2009 at 08:16:02PM +0000, corvid wrote:
Jorge wrote:
I added a new function call to the CCC API (wrapping the trick of the previous patch) and used it in three parts of the code. Please check the tip.
If I'm not connected and I try to go to a host that I have listed in /etc/hosts, then ^Q gives me a segfault.
Another SEGFAULT path was: load dillo home disconnect Internet click 9years press stop
All of these should be working now. Please report any further problem you find. I'll try to make the empty cache entries removal now, and then look for a way to hook the concurrent connection limit without memory leaks.
I just got a segfault on NULL Info when going to the https url for the uclinux page:
#0 0x0805cde1 in a_Chain_check (FuncStr=0x8118363 "a_Capi_ccc", Op=2, Branch=1, Dir=2, Info=0x0) at chain.c:191 #1 0x08063c72 in a_Capi_ccc (Op=2, Branch=1, Dir=2, Info=0x0, Data1=0x83e5ab0, Data2=0x0) at capi.c:522 #2 0x08063028 in Capi_conn_resume () at capi.c:172 #3 0x08063f10 in a_Capi_ccc (Op=2, Branch=1, Dir=1, Info=0x8cd2728, Data1=0x0, Data2=0x8122730) at capi.c:577 #4 0x0805cc80 in a_Chain_fcb (Op=2, Info=0x88224c0, Data1=0x0, Data2=0x8122730) at chain.c:113 #5 0x08086d95 in a_Dpi_ccc (Op=1, Branch=1, Dir=2, Info=0x88224c0, Data1=0x8b8d260, Data2=0x0) at dpi.c:625 #6 0x0805cd07 in a_Chain_bcb (Op=1, Info=0x8cd2728, Data1=0x8b8d260, Data2=0x0) at chain.c:136 #7 0x08063d6d in a_Capi_ccc (Op=1, Branch=1, Dir=2, Info=0x8cd2728, Data1=0x8936478, Data2=0x8b8d260) at capi.c:539 #8 0x08063b62 in a_Capi_dpi_send_cmd (url=0x8f1ef08, bw=0x81df6e8, cmd=0x8ee2400 "<cmd='open_url' url='https://blackfin.uclinux.org/gf/project/uclinux-dist/forum/?_forum_action=ForumMessageBrowse&thread_id=35676&action=ForumBrowse&forum_id=39' query='GET /gf/project/uclinux-dist/fo"..., server=0x8b8d260 "proto.https", flags=1) at capi.c:482 [snip]
Just committed a patch that's being a delight to test! :) It's the long waited for "empty cache entries removal". Now it's done automatically on clicking a new link, and manually with the Stop button. It doesn't sound impressive, but for instance, if you hit a blog site full of heavy images, hitting the Stop button will abort all the empty connections (not only stop rendering as in the past). This allows for much faster browsing, especially with low bandwidth, as the bandwidth is "rescued" from unwanted contents. Another gain happens when a requested link takes a long time to start flowing (e.g. ignored request by a busy browser). Just press stop, click the link again and there you are. Please test, and enjoy! BTW: I don't remember whether a fix for the uClinux URL above was already committed. It didn't SEGFAULT when testing tip. -- Cheers Jorge.-