MP crashed with VC++ runtime error (2 Viewers)

[petsa]

Hi gibman,

Have you had any chance to look anymore into the suspicious SVN? I'd be happy to test but I don't know how to make a build without the problematic SVN.

/Peter

 

[datfreak]

same here--- Has anyone found a workaround?

 

[Seidelin]

It is must likely related to the usage of "remember last active module".

I reverted "SVN 20891 - texture manager change"

seems to fix it ...

no more onresume problems on "remember last active module" for me.

Can any1 confirm ?

/gibman

I saw this issue once, but I do not have remember last active module activated.
Logs in pastebin

 

[petsa]

Has anyone tried the latest SVN against this problem?

/Peter

 

[Seidelin]

My test was performed with SVN 21013 iirc.

 

[nicksti]

hello,
same problem by me with latest svn but only after wakeup for recording. After waking up with keyboard or remote control I haven't had the problem.

 

[hoborg]

Same here. SVN Rev21026 doesn't fix it.

My logs:View attachment 30376

 

[Der_Bub]

Same with me, too. Crash after resume from hibernate

 

[petsa]

I think I got something here...

Out of curiousity I changed to another skin (Indigo) earlier today and all of a sudden I do not get these crashes anymore... Then I changed to Blue3, then Blue3wide, still no crashes. So I changed back to XmasBlue3Wide that I had originally and immediatly I got a crash upon resume.

Can anyone else confirm the chosen skin has something to do with this?

/Peter

 

[tourettes]

I think I got something here...

Out of curiousity I changed to another skin (Indigo) earlier today and all of a sudden I do not get these crashes anymore... Then I changed to Blue3, then Blue3wide, still no crashes. So I changed back to XmasBlue3Wide that I had originally and immediatly I got a crash upon resume.

Can anyone else confirm the chosen skin has something to do with this?

Sounds like a pure luck with the results

Main issue is coming from the texture manager changes (fixes actually). Its most likely just different timing that amount of the textures (and their sizes) are triggering the bug.