Topic: MC Crashing - Android Phone is causing it (DLNA?) (Read 13752 times)

jmone · « **Reply #50 on:** January 04, 2018, 04:37:07 pm »

Let me know what you would like me to do.... I've a few more days before I'm back to work.

JimH · « **Reply #51 on:** January 04, 2018, 04:40:58 pm »

Bob,
AndrewFG had a suggestion above:

https://yabb.jriver.com/interact/index.php/topic,113536.msg785298.html#msg785298

Jim

bob · « **Reply #52 on:** January 05, 2018, 09:09:27 am »

Quote from: JimH on January 04, 2018, 04:40:58 pm

Bob,
AndrewFG had a suggestion above:

https://yabb.jriver.com/interact/index.php/topic,113536.msg785298.html#msg785298

Jim

I saw that and tried it as close as I could without triggering the issue which leads me to believe the crash dump would be more useful

jmone · « **Reply #53 on:** January 05, 2018, 02:34:15 pm »

How about I try:
- Uninstall
- Install 32-Bit : test
- load my library & settings : test
- Install 64-bit : test
- load my library & settings : test

JimH · « **Reply #54 on:** January 05, 2018, 03:40:00 pm »

I wonder if something at the network layer on the PC is getting confused.

If it were MC, you would think we'd see more problem reports. Still ...

bob · « **Reply #55 on:** January 05, 2018, 03:54:07 pm »

jmone and I tracked it down. It's something to do with the web browser (start) window. If that's not showing, no crash.

Nope, still an issue, sigh...

jmone · « **Reply #56 on:** January 05, 2018, 04:10:12 pm »

I think we are getting closer however.... I've created a new Library (Blank) on this instance and it is not crashing even though the settings (incl DLNA) are all the same. I'm now wondering if there is some particular item(s) in my library that could be triggering it.

jmone · « **Reply #57 on:** January 05, 2018, 04:49:32 pm »

So I imported all the my images into this new Temp library, and it is not crashing.

I then switched back to my Main Library and it is now not crashing!?!?! (maybe too soon to call it)

Q: If it continues to be stable I don't understand what has "fixed" it, given the two libraries are separate.... or could their have been something updated in my setup / Main library when I created and imported the pics into the Temp library?

AndrewFG · « **Reply #58 on:** January 05, 2018, 05:26:27 pm »

Quote from: jmone on January 05, 2018, 04:49:32 pm

So I imported all the my images into this new Temp library, and it is not crashing.

I then switched back to my Main Library and it is now not crashing!?!?! (maybe to soon to call it)

Q: If it continues to be stable I don't understand what has "fixed" it, given the two libraries are separate.... or could their have been something updated in my setup / Main library when I created and imported the pics into the Temp library?

The phone is sending a series of CDS:Search() requests for image items, with certain filter parameters, each with successive Offset-Index and Requested-Count values. So I would look at which image items in your library match the filter parameters (in particular matches with “edge” conditions). And also the Offset-Index and Request-Count values (perhaps MC thinks it has more images than it really does, and one of the last “matches” is falling off the edge, or perhaps MC doesn’t like requests for more items than it owns). Also think about duplicate image items that MC may count as two, but only returns as one item. Stuff like that..

PS a CDS:Search example is in this post: https://yabb.jriver.com/interact/index.php/topic,113536.msg785193.html#msg785193

jmone · « **Reply #59 on:** January 05, 2018, 05:32:08 pm »

@AndrewFG: That was kind of of my approach. I looked at the Capture to see when the MC starter returning garbage then imported those images into MC (the new Temp Library). When it did not crash I started importing the rest (in batches). When that did not crash either, I switched back to my Main Library, and for some reason it is now not crashing either. Good outcome for me but No Idea why it is now not crashing.

JimH · « **Reply #60 on:** January 05, 2018, 06:41:48 pm »

Cosmic rays.

AndrewFG · « **Reply #61 on:** January 05, 2018, 08:47:54 pm »

Quote from: JimH on January 05, 2018, 06:41:48 pm

Cosmic rays.

I’m surprised you didn’t mention AV ..

jmone · « **Reply #62 on:** January 05, 2018, 09:48:25 pm »

Yeah well it crashed again.... and it was when my phone moved between WAP. Looking at the last part of the latest log, it is something to do with my image library requests. I have a bunch of these

Code: [Select]

4475937: 17440: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.67: POST: http://192.168.1.10:52102/ContentDirectory/control
14475937: 17440: Sharing Plugins: CDLNADeviceServerWorker::ProcessPost: Start
14475937: 17440: Sharing Plugins: CContentDirectoryService::HandleControlFunction: Start
14475937: 17440: Sharing Plugins: CContentDirectoryService::HandleControlFunction: Action: Search
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: Start
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: Search: upnp:class derivedfrom "object.item.imageItem"
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: 1
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: 2
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: 3a
14475937: 17440: Sharing Plugins: CMCViewInfoTree::GetSearchFilesItem: Start
14475937: 17440: Sharing Plugins: CMCViewInfoTree::GetSearchFilesItem: Hash: 8690193089776076918
14475937: 17440: Sharing Plugins: CMCViewInfoTree::GetSearchFilesItem: Finish (0 ms)
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: 3d
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: 4
14475937: 17440: Sharing Plugins: CContentDirectoryService::Search: 4a
14475953: 17440: Sharing Plugins: CContentDirectoryService::Search: Matching container: 1000 (has 14949 children)
14475953: 17440: Sharing Plugins: CContentDirectoryService::Search: 4e
14475953: 17440: Sharing Plugins: CContentDirectoryService::Search: 5
14475953: 17440: Sharing Plugins: CContentDirectoryService::Search: Finish (16 ms)
14475953: 17440: Sharing Plugins: CContentDirectoryService::HandleControlFunction: Finish (16 ms)
14475953: 17440: Sharing Plugins: CDLNADeviceServerWorker::ProcessPost: Finish (16 ms)

jmone · « **Reply #63 on:** January 05, 2018, 09:51:28 pm »

..then there starts to be errors mixed in such as:

Code: [Select]

14518984: 14040: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.96: SUBSCRIBE: http://192.168.1.10:52100/ContentDirectory/event
14518984: 12792: Sharing Plugins: CContentDirectoryService::HandleControlFunction: Start
14518984: 12792: Sharing Plugins: CContentDirectoryService::HandleControlFunction: Action: Search
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: Start
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: Search: upnp:class derivedfrom "object.item.imageItem"
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: 1
14518984: 8280: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: 2
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: 3a
14518984: 12792: Sharing Plugins: CMCViewInfoTree::GetSearchFilesItem: Start
14518984: 13264: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
14518984: 8280: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
14518984: 12792: Sharing Plugins: CMCViewInfoTree::GetSearchFilesItem: Hash: 8690193089776076918
14518984: 8280: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
14518984: 12792: Sharing Plugins: CMCViewInfoTree::GetSearchFilesItem: Finish (0 ms)
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: 3d
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: 4
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: 4a
14518984: 9868: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
14518984: 9868: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
14518984: 9868: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
14518984: 14040: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
14518984: 13264: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.135: SUBSCRIBE: http://192.168.1.10:52100/ContentDirectory/event
14518984: 14040: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
14518984: 3336: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
14518984: 3336: Sharing Plugins: CHTTPRequestMessage::ReadPreamble: Failed to read Method
14518984: 3336: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
14518984: 13264: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
14518984: 13264: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
14518984: 12792: Sharing Plugins: CContentDirectoryService::Search: Matching container: 1000 (has 14949 children)
14518984: 8512: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
14518984: 8512: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (43125 ms)

AndrewFG · « **Reply #64 on:** January 06, 2018, 04:54:30 am »

Yup it’s the CDS:Search alright. It seems to work fine when the searches are neatly serialized. But when the calls come thick and fast, and possibly overlapped, then it falls over. I would look into whether MCs SOAP implementation in general, or its CDS Search implementation, is fully thread safe code..

bob · « **Reply #65 on:** January 06, 2018, 10:54:38 am »

The Failed to read method messages are normal. It's a generic message in the http server code that appears with the SSDP stuff since it doesn't have a "method".

That doesn't rule out the search being an issue though. It would be nice if you could get a crash from the build I sent you. It would pin down the location. You'd probably need your material from the troublesome machine as well as the built thumbnails. You might want to do the Help->System Info on the Windows machine to see if they are all built.

jmone · « **Reply #66 on:** January 06, 2018, 08:10:11 pm »

HI Bob - I checked, All thumbs are built (for Images anyway). I'm running out of time for now to get that build up (I'll need to setup a new box as my exisitng one is headless Ubuntu).

jmone · « **Reply #67 on:** January 06, 2018, 11:43:10 pm »

Finally got it setup on Ubuntu 16.04 LTS. Took 3 goes of installing the OS / MC etc before I could get MC to install and run. Windows looks good to me! I'll let you know if either crash again.

jmone · « **Reply #68 on:** January 07, 2018, 02:22:02 pm »

Hi Bob, The Linux build crashed overnight (not sure why). Ran up MC again to output the logs but the logs are all really small and there is no Crash dump. Is this right? (note: logging is ON).

jmone · « **Reply #69 on:** April 19, 2018, 06:43:13 pm »

Arggg still crashing in MC24. This time my phone was syncing a few items, and I had to wait till it was finished or MC would just crash over and over. Log attached but it looks like all the rest.

jmone · « **Reply #70 on:** April 19, 2018, 06:44:53 pm »

Would a Memory Dump help?

bob · « **Reply #71 on:** April 20, 2018, 03:02:55 pm »

Quote from: jmone on April 19, 2018, 06:43:13 pm

Arggg still crashing in MC24. This time my phone was syncing a few items, and I had to wait till it was finished or MC would just crash over and over. Log attached but it looks like all the rest.

The crash dump would be awesome!

jmone · « **Reply #72 on:** April 20, 2018, 06:15:04 pm »

Got a DMP for both MC24 and JRWeb. I'll PM you the link when it has finished uploading.

bob · « **Reply #73 on:** April 23, 2018, 11:01:16 am »

Quote from: jmone on April 20, 2018, 06:15:04 pm

Got a DMP for both MC24 and JRWeb. I'll PM you the link when it has finished uploading.

Got it.
It appears to be crashing in JRWeb. Are you using Chromium or the native browser?

jmone · « **Reply #74 on:** April 23, 2018, 04:06:55 pm »

Native (IE), but swaping to Chromium does not help, still crashes within seconds (let me know if you want more logs, tests etc).

bob · « **Reply #75 on:** April 23, 2018, 04:19:22 pm »

Quote from: jmone on April 23, 2018, 04:06:55 pm

Native (IE), but swaping to Chromium does not help, still crashes within seconds (let me know if you want more logs, tests etc).

It's in the message loop. I can't see why it should be crashing there.
Can you package up a new set of dumps so I can see if the crash location changes?

jmone · « **Reply #76 on:** April 23, 2018, 04:30:49 pm »

Dump uploading (with Chromium as the browser). Liking my new faster upload speed! Anyway will PM the link shorly.

jmone · « **Reply #77 on:** April 27, 2018, 04:45:03 pm »

Hey bob - any luck with that 2nd Dump File?

bob · « **Reply #78 on:** April 30, 2018, 02:29:22 pm »

Quote from: jmone on April 27, 2018, 04:45:03 pm

Hey bob - any luck with that 2nd Dump File?

No, unfortunately it's not giving a break where the crash is.
I took a look at the search again and have been testing it a bit this morning.
There doesn't seem to be any threading issues in there, there is a lock around the view retrieval.
It sure would be useful to be able to duplicate this.

bob · « **Reply #79 on:** April 30, 2018, 02:57:59 pm »

Quote from: bob on April 30, 2018, 02:29:22 pm

No, unfortunately it's not giving a break where the crash is.
I took a look at the search again and have been testing it a bit this morning.
There doesn't seem to be any threading issues in there, there is a lock around the view retrieval.
It sure would be useful to be able to duplicate this.

I think we have something to try. I'll PM you with a test build.

jmone · « **Reply #80 on:** April 30, 2018, 03:02:30 pm »

That would be great as otherwise I'm thing of changing phone's. I'll be away for a few days so no rush.

bob · « **Reply #81 on:** April 30, 2018, 03:42:14 pm »

Quote from: jmone on April 30, 2018, 03:02:30 pm

That would be great as otherwise I'm thing of changing phone's. I'll be away for a few days so no rush.

You've got a link to the DL now.
Please don't change phones, it will be nice to fix this!
Thanks!

jmone · « **Reply #82 on:** May 03, 2018, 03:56:16 am »

Still crashing, next log send by PM. Thanks for the persistence.

jmone · « **Reply #83 on:** May 03, 2018, 04:12:47 am »

I think you are on the right path!!!! I had 3 DLNA renderers (say low, med, high). If I delete them all and just add "Generic DLNA" then MC does not crash. If I then add "Audiophile", MC will then crash.

bob · « **Reply #84 on:** May 03, 2018, 09:17:54 am »

Quote from: jmone on May 03, 2018, 04:12:47 am

I think you are on the right path!!!! I had 3 DLNA renderers (say low, med, high). If I delete them all and just add "Generic DLNA" then MC does not crash. If I then add "Audiophile", MC will then crash.

Weird because in that last test build we added a lock to handle just that situation, will keep looking.

jmone · « **Reply #85 on:** May 03, 2018, 03:54:04 pm »

I think you have it licked

No crashing so far with the latest test build!

bob · « **Reply #86 on:** May 03, 2018, 04:24:48 pm »

Quote from: jmone on May 03, 2018, 03:54:04 pm

I think you have it licked No crashing so far with the latest test build!

Thanks for the report, fingers crossed!

jmone · « **Reply #87 on:** May 04, 2018, 02:15:32 am »

It's been good all day. No crashes and no weirdness that I've noticed.

INTERACT FORUM

Author Topic: MC Crashing - Android Phone is causing it (DLNA?) (Read 13752 times)