Opened 11 years ago
Closed 11 years ago
#10242 closed bug (fixed)
WebPositive crash in network backend (corrupted memory)
| Reported by: | stippi | Owned by: | pulkomandy |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/WebPositive | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
From looking at the stack traces of the BUrlProtocol.HTTP threads, is there the same BString being modified concurrently?
Attachments (2)
Change History (7)
by , 11 years ago
| Attachment: | WebPositive-3129-debug-24-11-2013-20-44-35.report added |
|---|
comment:1 by , 11 years ago
Each of the BUrlProtocol.HTTP thread is bound to a BHttpRequest object and using the matching fOutputBuffer, so I don't think they are accessing the same string concurrently.
The intended use is: the output buffer is filled with the headers and request content, then the thread is started and reads from that string to send things over the network.
I will add some checks to make sure the string isn't modified again after the thread is started. Maybe a BMallocIO would be a better choice than a BString, as well.
comment:2 by , 11 years ago
I removed the fOutputBuffer BString in hrev46448, instead writing data directly into the socket. If anyone can reproduce this, an updated crash report is welcome.
by , 11 years ago
| Attachment: | WebPositive-1944-debug-21-12-2013-09-18-16.report added |
|---|
comment:3 by , 11 years ago
I can reproduce it in hrev46573 by dragging /boot/system/data/gutenprint/dither-matrix-1x1.xml into Web+ window serveral (>3) times
Debugger crash report