Processing of dumps for applications written on JavaScript

Question

We have published in Windows Store our application which is written on html5/JavaScript. We receive the follow dumps: "Most common reasons why your app is not responsive" and "Most common crashes". The problem is we can't process those dumps because the callstack doesn't contain JavaScript calls. We used Visual Studio and WinDBG. We are interested is there a way to obtain useful information from dumps? Any ideas are appreciated.

Answer 1

I've never looked at a javascript dump - do you mind sharing it so I can see what we can do?

---

Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.

NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

Answer 2

Sure. What is the best way to share it? Tnx.

Answer 3

Please post it to OneDrive and share a link here.

---

Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.

NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

Answer 4

https://onedrive.live.com/redir?resid=340FE2FBFC915FFA!150&authkey=!AJkczMRyfq4hR3E&ithint=file%2ccab

https://onedrive.live.com/redir?resid=340FE2FBFC915FFA!149&authkey=!AG-c_oFN-nZmKMA&ithint=file%2ccab

Answer 5

Hello, is there any news? Do you need anything else?

Answer 6

I'm going to run this through an analyzer here and let you know the results.

---

Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.

NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

Answer 7

It looks like it is failing in rlls64.dll which looks like a 3rd party adware program called relevant knowledge. Are you using that in your product?

---

Bret Bentzinger (MSFT) @awehellyeah

Answer 8

Hello,

No, we haven't used any 3rd party programs here.

Answer 9

Hi Nano.  After further research this is spyware running on the machine that generated the dump file.   So I would say your application is fine and no problems.   If it is possible to reach out to your customer that reported this issue, then you may want to send them this link on removing the spyware:

http://www.ehow.com/how_5634500_remove-relevant-knowledge-spyware.html

---

Bret Bentzinger (MSFT) @awehellyeah

Answer 10

Thank you for your reply.

We can't contact our customer because we get those dumps through Windows Store, in fact from Microsoft, so they are impersonal.

I'd like to ask, is your conclusion applicable for both dumps we uploaded before?

Also we are interested what to do with other dumps (we have got about 8). Do we need to send them to you for analysis?

Thank you.

Answer 11

I can't believe I didn't post this earlier, but here is blog post on how you can set up a tool called DebugDiag to look at your dumps:

http://blogs.msdn.com/b/wsdevsol/archive/2014/06/26/automating-analysis-of-windows-store-crash-reports.aspx

---

Bret Bentzinger (MSFT) @awehellyeah

Answer 12

Thank you very much for your reply.

We tried that recommended tool but found nothing more than we could see using Visual Studio or WinDbg.

There in call stack we can see only Window's API calls. We suggest that it is possible that we use API incorrectly. But we can't identify which exact functions are performed because all calls are presented in JS code.

Can you give us advice how to manage it?

Please let me know if you need any additional information from us.

Thank you.

Answer 13

Not sure what you are asking here.   Is this a new issue?  The original issue is due to spyware on the machine.

You are correct, there isn't great support for post mortem debugging with javascript.  

---

Bret Bentzinger (MSFT) @awehellyeah

Answer 14

Let me explain.

It is the same issue. Yes, we got information about one dump you analyzed. But we have right now 10 dumps and expect to have more in the future. The information about problems from a client's side are not important for us because we can't contact them and advise anything. But we need the information about problems with our app which are reflected in these dumps. Is there any way to get this kind of information from our dumps or they are the kind of vain stuff for us?

Thank you.

Answer 15

DebugDiag will automate what you can do with a debugger like windbg.   If that does not give you the results you need, then you will need to open the dumps in windbg and analyze them manually.   That is way outside the scope of a forum post though.

This channel 9 video has some good pointers on where to start with the debugging though.

http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-64-Windows-81-Store-App-Crash-c000027b

---

Bret Bentzinger (MSFT) @awehellyeah