Summary: | [GTK] libsoup critical warnings | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Philippe Normand <pnormand> | ||||||
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | abarth, eric, svillar, webkit.review.bot | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | PC | ||||||||
OS: | OS X 10.5 | ||||||||
Attachments: |
|
Description
Philippe Normand
2011-02-16 08:08:30 PST
Created attachment 82639 [details]
proposed patch
Comment on attachment 82639 [details] proposed patch View in context: https://bugs.webkit.org/attachment.cgi?id=82639&action=review > Source/WebCore/platform/network/soup/ResourceHandleSoup.cpp:703 > + SoupMessage* soupMessage = d->m_soupMessage.get(); > + if (SOUP_STATUS_IS_SUCCESSFUL(soupMessage->status_code)) > + return; Hrm. Wouuld it be better to check for soupMessage->status_code != SOUP_STATUS_NONE? We don't want to cancel the message if it's finished for any reason. Created attachment 82648 [details]
proposed patch
Committed r78798: <http://trac.webkit.org/changeset/78798> http://trac.webkit.org/changeset/78798 might have broken GTK Linux 32-bit Debug |