Opened 3 years ago
Closed 2 years ago
#17409 closed bug (fixed)
WebPositive crash - BUrlProtocol.HTTP abort
Reported by: | kallisti5 | Owned by: | pulkomandy |
---|---|---|---|
Priority: | high | Milestone: | R1/beta4 |
Component: | Kits/Web Kit | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
x86_64, hrev55643
_kern_debugger abort /boot/system/lib/libWebKitLegacy.so.1.8.3 WebCore::BUrlRequestWrapper::Write BDataIo::WriteExactly BPrivate::Network::BHttpRequest::_MakeRequest BPrivate::Network::BHttpRequest::_ProtocolLoop BPrivate::Network::BUrlRequest::_ThreadEntry thread_entry
Attachments (1)
Change History (4)
by , 3 years ago
Attachment: | webpositive-crash.png added |
---|
comment:1 by , 3 years ago
comment:2 by , 3 years ago
Component: | Applications/WebPositive → Kits/Web Kit |
---|---|
Keywords: | webkitlegacy removed |
Does this still occur? it looks like the same issue as https://dev.haiku-os.org/ticket/17383 to me.
comment:3 by , 2 years ago
Milestone: | Unscheduled → R1/beta4 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Switched to curl for the next release so this class won't be used anymore.
Note:
See TracTickets
for help on using tickets.
Probably same problem/related to #17356. Since the changes of the service kit, BUrlProtocolHandler writes to a BDataIO directly instead of chanelling data through a BMessage. This breaks WebKit which expects everything to happen from the main thread.
Basically the service kit changes (from leorize's GSoC work) made the asynchronous mode unusable for WebKit because it is not fully asynchronous, and some things happen in the HTTP thread where they should really be forwarded to another thread.