Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes with 04-30-07 #10

Closed
Chronial opened this issue May 1, 2016 · 6 comments
Closed

Crashes with 04-30-07 #10

Chronial opened this issue May 1, 2016 · 6 comments

Comments

@Chronial
Copy link
Collaborator

Chronial commented May 1, 2016

Activating DSCM-Net causes my dark souls to crash in irregular intervals. Here's a dump from one of these crashes. DARKSOULS-mini.zip

I assume that it's just the normal dscm connection attempt that causes the crash, since the irc feature causes that code to be called a lot more.

@Wulf2k
Copy link
Owner

Wulf2k commented May 1, 2016

Weird, i haven't experienced a crash for several versions now, and i left
it running for a couple hours yesterday.

I'll take a look at it later tonight.

On May 1, 2016 11:22, "Chronial" [email protected] wrote:

Activating DSCM-Net causes my dark souls to crash in irregular intervals.
Here's a dump from one of these crashes. DARKSOULS-mini.zip

I assume that it's just the normal dscm connection attempt that causes
the crash, since the irc feature causes that code to be called a lot more.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

@Chronial
Copy link
Collaborator Author

Chronial commented May 1, 2016

I added some logging to see whether the game crashed when dscm tried to initiate a connection. That is not the case, but I discovered #13. In fact, as 40 connections where initiated at startup the nodecode went to 20 instantly and never came back down, so dscm never initated another connection after startup.

#13 might actually be the cause of this bug – maybe the connection storm that dscm causes on startup gets something into an invalid state, which triggers this crash later on. My most recent crash came in the exact moment I pressed "summon phantom" on a summoning sign.

@Wulf2k
Copy link
Owner

Wulf2k commented May 2, 2016

Just to be sure, are you running PVP watchdog?

Have you ruled out the namecrash?
On May 1, 2016 5:54 PM, "Chronial" [email protected] wrote:

I added some logging to see whether the game crashed when dscm tried to
initiate a connection. That is not the case, but I discovered #13
#13. In fact, as 40
connections where initiated at startup the nodecode went to 20 instantly
and never came back down, so dscm never initated another connection after
startup.

#13 #13 might actually be
the cause of this bug – maybe the connection storm that dscm causes on
startup gets something into an invalid state, which triggers this crash
later on. My most recent crash came in the exact moment I pressed "summon
phantom" on a summoning sign.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#10 (comment)

@Wulf2k
Copy link
Owner

Wulf2k commented May 2, 2016

Install watchdog and see if the crashes go away.

Players with names over 15 characters will crash you without it.
On May 1, 2016 21:57, "Chronial" [email protected] wrote:

nope, only dscm and dsfix.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#10 (comment)

@Chronial
Copy link
Collaborator Author

Chronial commented May 2, 2016

Ah, didn't know about the namecrash. I am again and again surprised by the shittiness of that port ^^. Installed PVP watchdog and will report back :). Can't play as much during the week though.

@Chronial
Copy link
Collaborator Author

Chronial commented May 2, 2016

Installed PVP watchdog, but also #16. Crashes are gone now, so closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants