INTERACT FORUM

More => Old Versions => JRiver Media Center 21 for Windows => Topic started by: HiFiTubes on January 12, 2016, 11:21:00 am

Title: Crash updating view scheme
Post by: HiFiTubes on January 12, 2016, 11:21:00 am
Crash after updating a view scheme's Set Rules for File Display:

2379921: 4188: Database: CSearchFilesHelper::GetResults: Search: [Media Type]=[Audio]; Elapsed ms: 23.828
2379953: 4188: Database: CMediaFileIOLoad::Load: Loading: C:\Users\x64\AppData\Roaming\J River\Media Center 21\Library\Cache\File List Sort\Cache (22).dat
2380875: 4188: General: CPanesWnd::UpdatePanes: Finish (985 ms)
2380875: 4188: General: CMJFileListCtrl::StartFileInsertion: Start
2380890: 4188: Database: CMediaDatabase::RemoveFileAbsolute: Filename:  Mode: 0  Track: 0
2380890: 4188: General: CMJFileListCtrl::StartFileInsertion: Finish (15 ms)
2380890: 4188: General: CMJFileListCtrl::FinishFileInsertion: Start
2380890: 4188: General: CMJFileListCtrl::SetItemCount: Start
2381359: 4188: Database: CMediaDatabase::RemoveFileAbsolute: Filename:  Mode: 0  Track: 0
2381437: 4188: General: CMJFileListCtrl::SetItemCount: Finish (547 ms)
2381656: 4188: General: CMJFileListCtrl::FinishFileInsertion: Finish (766 ms)
2381671: 4188: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
2381671: 4188: General: TopLevelExceptionFilter: Message: 275, wParam: 6001, lParam: 0
2381843: 4188: General: TopLevelExceptionFilter: MiniDumpWriteDump: 1
2386297: 5752: General: JRWebApp::Destroy: Start
2386297: 5752: General: JRWebApp::Destroy: Finish (0 ms)
2386297: 5752: General: JRWebApp::Run: Finish (2386266 ms)
2386297: 5752: General: JRWebApp::ExitInstance: Start
2386297: 5752: General: JRWebApp::ExitInstance: Stopping web engine
2386344: 5752: General: JRWebApp::ExitInstance: Stopping callback server
2386344: 5752: General: JRWebApp::ExitInstance: Stopping interface server
2386344: 5752: General: JRIpcServerThreaded::ServerStop: Start
2386344: 5752: General: JRIpcServerThreaded::ServerStop: Canceling thread
2386344: 5752: General: JRIpcServerThreaded::ServerStop: Canceling pending run
2386344: 5752: General: JRIpcServerThreaded::ServerStop: Stopping thread
2386344: 212: General: JRIpcServerThreaded::Thread: Thread finishing (cancel: 1; errors: 1)
2386344: 212: General: JRIpcServerThreaded::Thread: Finish (2386328 ms)
2386375: 5752: General: JRIpcServerThreaded::ServerStop: Canceling response threads
2386375: 5752: General: JRIpcServerThreaded::ServerStop: Deleting response threads
2386375: 5752: General: JRIpcServerThreaded::ServerStop: Closing notification window
2386375: 5752: General: JRIpcServerThreaded::ServerStop: Finish (31 ms)
2386375: 5752: General: JRWebApp::ExitInstance: Finishing
Title: Crash updating view scheme
Post by: Hendrik on January 12, 2016, 12:00:42 pm
Posting those log excerpts doesn't help us at all. If you want to report a crash please post the full log package (zip file, generated by Help -> Logging-> Report problem..) or mail it to logs at jriver dot com
Title: Re: Crash updating view scheme
Post by: JimH on January 12, 2016, 12:11:00 pm
Are you using Nvidia video?
Title: Re: Crash updating view scheme
Post by: HiFiTubes on January 13, 2016, 03:33:03 am
Quote from: JimH on January 12, 2016, 12:11:00 pm
Are you using Nvidia video?

Yes, thanks. Log attached.

Title: Re: Crash updating view scheme
Post by: Hendrik on January 13, 2016, 03:36:09 am
I explained how to generate a valid log package in my previous post, please post the full and unmodified package right after a crash, anything else does not help us to debug crashes.

Just to make sure:
(1) Reproduce the crash
(2) Start MC again
(3) Help -> Logging -> Report Problem
(4) Zip File with all required information will be placed on your desktop
Title: Re: Crash updating view scheme
Post by: JimH on January 13, 2016, 03:51:58 am
There have been several similar problems recently that were found to be related to Nvidia drivers.  Start reading, with this post and continue on:
http://yabb.jriver.com/interact/index.php?topic=24031.msg704783#msg704783

I'm guessing that Win10 may also be a factor.
Title: Re: Crash updating view scheme
Post by: HiFiTubes on January 13, 2016, 04:08:55 am
Quote from: Hendrik on January 13, 2016, 03:36:09 am
I explained how to generate a valid log package in my previous post, please post the full and unmodified package right after a crash, anything else does not help us to debug crashes.

Just to make sure:
(1) Reproduce the crash
(2) Start MC again
(3) Help -> Logging -> Report Problem
(4) Zip File with all required information will be placed on your desktop

Thanks. Is this a sticky?

I'm confused how this process will let me send you an old/previous log? At this point the previous log was too "new", and I had to send you older one. I can add system info for you.
Title: Re: Crash updating view scheme
Post by: HiFiTubes on January 13, 2016, 04:14:08 am
Quote from: JimH on January 13, 2016, 03:51:58 am
There have been several similar problems recently that were found to be related to Nvidia drivers.  Start reading, with this post and continue on:
http://yabb.jriver.com/interact/index.php?topic=24031.msg704783#msg704783

I'm guessing that Win10 may also be a factor.
Last crash I had here was when I clicked Detach Display. I will capture a log for that one soon.

I'm using the most up to date Nvidia drivers, still hoping for better native screen switching support from MC regardless of Win OS. It's the only app I use that doesn't respond Win + arrow keys. It does respond to the new Shift + Win + arrow keys but only in a non-maximized state. The old jump to shortcut doesn't work either.

 I understand the benefits of how MC is designed possibly outweigh this need but still, I am hopeful someday it will integrate more peacefully.
Title: Re: Crash updating view scheme
Post by: CountryBumkin on January 13, 2016, 01:41:02 pm
Quote from: HiFiTubes on January 13, 2016, 04:08:55 am
Thanks. Is this a sticky?

I'm confused how this process will let me send you an old/previous log? At this point the previous log was too "new", and I had to send you older one. I can add system info for you.

When you create a new Log after a crash and a restart, the log package (the zip file) has the "old log" prior to the crash and a "new log" for whatever happened after the restart. If there was a crash, the log will usually contain a dmp "dump" file too.