Reply to thread

Message

<blockquote data-quote="velis" data-source="post: 729886" data-attributes="member: 96429">Just a minor update. Unfortunately I can't post any code at this moment.I have found my bug(s). Turns out I didn't have a memory overrun, but rather a ton of bugs that I introduced when I was merging code together and introducing common classes. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" />Source is now even cleaner and understandable (I hope)Despite all the rearrangements, UDP remains super stable - so I'm very happy with this part. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />I'm still having issues with HTTP. I must figure out a sensible way of dynamically expanding buffers. Ran into this problem because the server returns chunk sizes around 20KB, but my internal buffers were at 16KB.Or perhaps I should just implement &quot;persistent chunk&quot; meaning that I would just blindly receive data until chunk size was satisfied.Anyway - when I figure this out, HTTP will be done.And before you ask: I don't like multi-MB memory usage for no purpose. Right now my filters take 128KB for buffers and 16KB for thread stack. Thread stack can go down to 4KB, but I don't want to push it. I'll just have to fix this &quot;inefficiency&quot; with a bit more code instead of more RAM, I hope.Ran out of time for RTP completion today <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />Otherwise progress is good and we should see some results by the end of the week. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" /></blockquote>

[QUOTE="velis, post: 729886, member: 96429"] Just a minor update. Unfortunately I can't post any code at this moment. I have found my bug(s). Turns out I didn't have a memory overrun, but rather a ton of bugs that I introduced when I was merging code together and introducing common classes. :ooops: Source is now even cleaner and understandable (I hope) Despite all the rearrangements, UDP remains super stable - so I'm very happy with this part. :) I'm still having issues with HTTP. I must figure out a sensible way of dynamically expanding buffers. Ran into this problem because the server returns chunk sizes around 20KB, but my internal buffers were at 16KB. Or perhaps I should just implement "persistent chunk" meaning that I would just blindly receive data until chunk size was satisfied. Anyway - when I figure this out, HTTP will be done. And before you ask: I don't like multi-MB memory usage for no purpose. Right now my filters take 128KB for buffers and 16KB for thread stack. Thread stack can go down to 4KB, but I don't want to push it. I'll just have to fix this "inefficiency" with a bit more code instead of more RAM, I hope. Ran out of time for RTP completion today :( Otherwise progress is good and we should see some results by the end of the week. :D [/QUOTE]

Verification