Menu
Forums
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Trending
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Upgrades
Log in
Register
What's new
Search
Search
Search titles only
By:
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Server Development
Habbo Retros
Habbo Q&A
PlusEMU Crash after 10-15 minutes
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Mikee" data-source="post: 428085" data-attributes="member: 76567"><p>Hard for me to gauge exactly since I don't know whats happening when, and what the full code is from the stack trace but my original thoughts were this.</p><p></p><p>Instead of try{}catch{} within the ToString method (never new sled coded one that inherited from the original one, pretty neat) but wrap a try{}Catch{} around the ToString line of code, then when you catch for an exception just pass through it, i.e. reassign</p><p>[CODE]Plus.Communication.Packets.Incoming.ClientPacket[/CODE] to null, and then return;</p><p>Also use</p><p>[CODE]catch(OutOfMemoryException e){</p><p>//Log it</p><p>Plus.Communication.Packets.Incoming.ClientPacket = null;</p><p>return;</p><p>}</p><p></p><p>instead of</p><p>catch(Exception e){}</p><p></p><p>Just bad practice and could cause issues later.[/CODE]</p><p></p><p>Again, hard for me to make a good judgement call without more info.</p><p>Let me know how it goes,</p></blockquote><p></p>
[QUOTE="Mikee, post: 428085, member: 76567"] Hard for me to gauge exactly since I don't know whats happening when, and what the full code is from the stack trace but my original thoughts were this. Instead of try{}catch{} within the ToString method (never new sled coded one that inherited from the original one, pretty neat) but wrap a try{}Catch{} around the ToString line of code, then when you catch for an exception just pass through it, i.e. reassign [CODE]Plus.Communication.Packets.Incoming.ClientPacket[/CODE] to null, and then return; Also use [CODE]catch(OutOfMemoryException e){ //Log it Plus.Communication.Packets.Incoming.ClientPacket = null; return; } instead of catch(Exception e){} Just bad practice and could cause issues later.[/CODE] Again, hard for me to make a good judgement call without more info. Let me know how it goes, [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Server Development
Habbo Retros
Habbo Q&A
PlusEMU Crash after 10-15 minutes
Top