alibaba / alibaba/anyproxy

AnyProxy遇到异常退出了

Open
#126 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
7.9k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

平台系统:windows7旗舰版,32位
AnyProxy版本:3.10.3

异常堆栈信息(下面是遇到的2种异常,发生的都非常偶然,大概一天能碰到一次):
Caught exception: RangeError: Array buffer allocation failed
at Buffer.Uint8Array (native)
at FastBuffer (buffer.js:11:5)
at createUnsafeBuffer (buffer.js:38:12)
at allocate (buffer.js:181:12)
at Function.Buffer.allocUnsafe (buffer.js:141:10)
at Function.Buffer.concat (buffer.js:309:23)
at D:\Programs\nodejs\node_global\node_modules\anyproxy\lib\requestHandler.j
s:179:52
at D:\Programs\nodejs\node_global\node_modules\anyproxy\node_modules\async\l
ib\async.js:607:21
at D:\Programs\nodejs\node_global\node_modules\anyproxy\node_modules\async\l
ib\async.js:246:17
at iterate (D:\Programs\nodejs\node_global\node_modules\anyproxy\node_module
s\async\lib\async.js:146:13)
AnyProxy is about to exit with code: 0

Caught exception: TypeError: The header content contains invalid characters
at ClientRequest.OutgoingMessage.setHeader (_http_outgoing.js:358:11)
at new ClientRequest (_http_client.js:86:14)
at Object.exports.request (http.js:31:10)
at dealWithRemoteResonse (D:\Programs\nodejs\node_global\node_modules\anypro
xy\lib\requestHandler.js:145:65)
at routeReq (D:\Programs\nodejs\node_global\node_modules\anyproxy\lib\reques
tHandler.js:88:13)
at D:\Programs\nodejs\node_global\node_modules\anyproxy\node_modules\async\l
ib\async.js:607:21
at D:\Programs\nodejs\node_global\node_modules\anyproxy\node_modules\async\l
ib\async.js:246:17
at iterate (D:\Programs\nodejs\node_global\node_modules\anyproxy\node_module
s\async\lib\async.js:146:13)
at D:\Programs\nodejs\node_global\node_modules\anyproxy\node_modules\async\l
ib\async.js:157:25
at D:\Programs\nodejs\node_global\node_modules\anyproxy\node_modules\async\l
ib\async.js:248:21
AnyProxy is about to exit with code: 0

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in lib/requestHandler.js at the paths shown near lines 88, 145, and 179, then review the two stack traces separately. Reproduce or characterize the failures on the reported Windows 7 32-bit setup, focusing on the buffer concatenation and remote-response request paths. Done means the intermittent exceptions are understood and AnyProxy no longer exits unexpectedly in those cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.