Topic: Randomly crashing while idle (Read 8670 times)

justsomeguy · « **on:** July 30, 2013, 02:07:49 am »

I've been having this problem for a while now actually and have just been dealing with it. I have MC installed on my htpc, it is acting as a media server to other clients in the house. This htpc doesn't get used very often and mostly just sits there serving other clients. Periodically a client will not be able to connect. I log into the server and MC has crashed. This can happen just sitting and I know that no clients have connected since it was working last. This can happen every couple days or once a week.
I have enabled logging and have a log now from the last crash. Where could a send this to to possibly see what the problem is?

Thanks

WeeHappyPixie · « **Reply #1 on:** July 30, 2013, 02:15:44 am »

I too have been experiencing this problem. Last night I tried reinstalling build 211 and still had problem. I then created a new test library from scratch and problem remains.

This has happened in the last few builds.

John

pqcgebxm · « **Reply #2 on:** July 30, 2013, 04:56:39 am »

I hope you can help. In the last few months, my Media Center has crashed regularly -- about once a day. There's no error message, etc; instead, the process just exits without notice. Also, I can't reproduce by taking some action... it just crashes after some period of time.

I turned on logging and captured the last crash -- I'll attache the log report as an update.

Are there any known issues with this build (I think it's the stable version)? Is there any further information I can provide?

pqcgebxm · « **Reply #3 on:** July 30, 2013, 05:00:33 am »

I tried to attache the log report that was generated (.zip), but it was rejected because it was about 2m. So, I've attached it after removing "Previous Log.txt" (which was very large). Is "Previous Log.txt" needed?

Alex B · « **Reply #4 on:** July 30, 2013, 05:44:03 am »

Random crashes may be caused by quite a number of different things. My MC18 instances on three different PCs have been very stable.

The previous crash incident would have been in the previous log (if logged at all). The "log.txt" file contains only the events from the current MC session (after the program restart.)

You could periodically reset the log in "Help > Logging" until the crash occurs to get a smaller log file.

In any case you could upload the zip file to some online service and post a link (e.g. Dropbox, SkyDrive, SugarSync, etc.)

JRiver has also a mail address for logs, but it is probably better to wait a reply from JRiver before sending logs by email.

JimH · « **Reply #5 on:** July 30, 2013, 07:01:37 am »

The wiki has a topic called "Stability".

18.0.211 is at the top of the MC18 board.

JimH · « **Reply #6 on:** July 30, 2013, 07:08:09 am »

Quote from: justsomeguy on July 30, 2013, 02:07:49 am

I have enabled logging and have a log now from the last crash. Where could a send this to to possibly see what the problem is?

logs at jriver. Include a link to this thread.

justsomeguy · « **Reply #7 on:** July 30, 2013, 09:25:28 pm »

Sent, thanks

Matt · « **Reply #8 on:** August 02, 2013, 09:50:28 am »

I believe it's crashing when loading EPG data using mc2xml.

Please try Options > Television > Load program guide... and use the 'Download EPG automatically' method.

Does that solve the issues?

justsomeguy · « **Reply #9 on:** August 02, 2013, 08:45:18 pm »

It was set for mc2xml. I'm not using MC for TV so I may just disable the TV portion all together but for now I've made the change you suggested just to trouble shoot if that is the problem. I'll update in a few days with the results.

Thanks

pqcgebxm · « **Reply #10 on:** August 05, 2013, 12:39:22 am »

I have this problem too -- I started a thread here:

http://yabb.jriver.com/interact/index.php?topic=82397.0

I've been running the stable build, but I've just updated to the latest build (18.0.211) and will see if that resolves anything.

I checked my "Load program guide" -- I had disabled the TV feature, but I re-enalbed it to check my previous setting -- it was set to "Download EPG automatically", so that's definitely not related to the behaviour I'm seeing.

pqcgebxm · « **Reply #11 on:** August 05, 2013, 12:41:18 am »

Quote from: JimH on July 30, 2013, 07:01:37 am

The wiki has a topic called "Stability".

I don't see anything here that's very relevant... I run a very lean media server -- no plugins, etc. -- and nothing has changed on the system in months. If the problem re-occurs, I'll provide a more in-depth report.

Quote from: JimH on July 30, 2013, 07:01:37 am

18.0.211 is at the top of the MC18 board.

I've just done this, and will send a log if the problem happens again.

BTW, the issue I'm seeing is very similar (maybe identical) to what justsomeguy has reported:

http://yabb.jriver.com/interact/index.php?topic=82394.0

AnalogRoaming · « **Reply #12 on:** August 05, 2013, 01:25:36 am »

I have to keep going back to 18.195 because it's the last version of MC that runs without crashing daily on my HTPC. It's just crashed twice in the last hour. Every version I've tried since has been unstable.

JimH · « **Reply #13 on:** August 05, 2013, 07:11:47 am »

Quote from: AnalogRoaming on August 05, 2013, 01:25:36 am

I have to keep going back to 18.195 because it's the last version of MC that runs without crashing daily on my HTPC. It's just crashed twice in the last hour. Every version I've tried since has been unstable.

Please report the build you're using and what you're doing when it happens.

AnalogRoaming · « **Reply #14 on:** August 05, 2013, 09:08:59 am »

JimH,

Anything over 18.195. I thought that was clear, sorry. And what I'm doing is watching a video. There's another thread regarding a screensaver issue.

JimH · « **Reply #15 on:** August 05, 2013, 09:33:10 am »

Including 18.0.211?

AnalogRoaming · « **Reply #16 on:** August 05, 2013, 09:53:20 am »

Yes sir.

Matt · « **Reply #17 on:** August 05, 2013, 09:56:42 am »

It's crashing in a background thread in ole32.dll. This is a system COM library.

We've had a couple other users report this when letting the program sit idle.

Unfortunately we don't know what might be causing this yet. If you find any extra clues, please share.

Sorry for the trouble.

JimH · « **Reply #18 on:** August 05, 2013, 10:16:07 am »

Please try 18.0.212:

http://yabb.jriver.com/interact/index.php?topic=82548.0

AnalogRoaming · « **Reply #19 on:** August 05, 2013, 02:20:37 pm »

Upgraded to 18.212 and it crashed right away. :/

But I restarted it several times and it didn't crash again.

pqcgebxm · « **Reply #20 on:** August 05, 2013, 04:35:46 pm »

I upgraded to 18.0.211 it it still crashed. I'll attach my log file.

I'll upgrade to 18.0.212 tonight to test that version.

justsomeguy · « **Reply #21 on:** August 05, 2013, 06:47:10 pm »

So far I haven't had it crash again. However it's only been 3 days, I have gone longer than this before crashing in the past. I'll hold off on updating to .212 until I get another crash, if i do.

pqcgebxm · « **Reply #22 on:** August 06, 2013, 04:03:18 am »

The "Stability" page on wiki suggest disabling plugins... however, I can no longer find the "Plugin Manager". It used to be under "Tools> Plug-in Manger..." but that option no longer appears. How can I disable all plugins?

Matt · « **Reply #23 on:** August 06, 2013, 12:26:00 pm »

Quote from: Sinnerman on August 06, 2013, 04:03:18 am

The "Stability" page on wiki suggest disabling plugins... however, I can no longer find the "Plugin Manager". It used to be under "Tools> Plug-in Manger..." but that option no longer appears. How can I disable all plugins?

Options > Services > Interface Plug-ins

pqcgebxm · « **Reply #24 on:** August 06, 2013, 06:28:43 pm »

I upgraded to 18.0.212 last night, but unfortunately it had crashed by this morning. I've attached the Media Center log, and also copied this from the crash dialog:

Problem signature:
Problem Event Name:   APPCRASH
Application Name:   Media Center 18.exe
Application Version:   18.0.212.0
Application Timestamp:   51ffbb75
Fault Module Name:   ole32.dll
Fault Module Version:   6.1.7601.17514
Fault Module Timestamp:   4ce7b96f
Exception Code:   c0000096
Exception Offset:   00048665
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   3081
Additional Information 1:   a7aa
Additional Information 2:   a7aa91f17ea749d42a4de3b390fa5b3d
Additional Information 3:   a7aa
Additional Information 4:   a7aa91f17ea749d42a4de3b390fa5b3d

I also grabbed a bunch of system (application) event entries, which may be related (these all occurred between the time I upgraded to 18.0.212 and when I found MC crashed this morning):

1) 7/08/2013 7:34:36 AM (this was the last event in the log -- maybe generated when Media Center crashed?)

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Media Center 18.exe
P2: 18.0.212.0
P3: 51ffbb75
P4: ole32.dll
P5: 6.1.7601.17514
P6: 4ce7b96f
P7: c0000096
P8: 00048665
P9:
P10:

Attached files:

These files may be available here:
C:\Users\Common\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Media Center 18._b275f4cfa1c3a457bf3187c9e2c34b690f263_19e1e59a

Analysis symbol:
Rechecking for solution: 0
Report Id: 49a2667c-fea1-11e2-af88-3c07540350e3
Report Status: 0

2) 7/08/2013 7:33:42 AM (this one is actually from the system log, not sure if it's related, but it happens just a minute before the one above)

The driver detected a controller error on \Device\Harddisk1\DR1.

3) 7/08/2013 12:05:46 AM

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Media Center 18 because of this error.

Program: Media Center 18
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
   - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
   - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

4) 7/08/2013 12:05:46 AM

Faulting application name: Media Center 18.exe, version: 18.0.212.0, time stamp: 0x51ffbb75
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96f
Exception code: 0xc0000096
Fault offset: 0x00048665
Faulting process id: 0x1c10
Faulting application start time: 0x01ce928a4b9cbd7e
Faulting application path: C:\Program Files (x86)\J River\Media Center 18\Media Center 18.exe
Faulting module path: C:\Windows\syswow64\ole32.dll
Report Id: 49a2667c-fea1-11e2-af88-3c07540350e3

hooli · « **Reply #25 on:** August 07, 2013, 05:42:32 am »

I also seem to have the same issue. Updated to newest version, woke up to crash notification again.

jmone · « **Reply #26 on:** August 07, 2013, 06:01:24 am »

FYI - Here was my report

Quote from: jmone on July 24, 2013, 06:01:23 pm

Ok - so here is what I've found out so far

- 23rd June : First ever OLE Crash and the HTPC was running 18.0.194 and the Server was running 18.0.202 / 203 (we were reporting crashes with the 203 version so rolled back).
- The only other thing that changed on the HTPC that day was Windows Update installed some bits a peicins but the big one was IE10

In looking at the even log, in most cases in the one second prior to MC crashing the OLE32 DLL
- There is Notification Event Logged by "Lights Out" that the WHS (this is our backup server) has a power event (eg been woken up I think)
- There is an Application Error logged by MC saying "Windows cannot access the file..." (see full code below)
- There is an Application Error logged by MC saying OLE32 had crased (as Matt as reported)

Code: [Select]
Log Name: Application Source: Application Error Date: 23/06/2013 6:20:04 AM Event ID: 1005 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: HT-PC Description: Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Media Center 18 because of this error. Program: Media Center 18 File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: 00000000 Disk type: 0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="49152">1005</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-06-22T20:20:04.000000000Z" /> <EventRecordID>23899</EventRecordID> <Channel>Application</Channel> <Computer>HT-PC</Computer> <Security /> </System> <EventData> <Data> </Data> <Data>Media Center 18</Data> <Data>00000000</Data> <Data>0</Data> </EventData> </Event>
So it seems it could be
- related to the crash issue Yaobing had seen on Network related playback around this time
- IE10
- The Winter Solstice (for the pagans in us all)

My "Fix" was I upgraded the HTPC to Win8. Not much help I know.

pqcgebxm · « **Reply #27 on:** August 07, 2013, 06:54:48 pm »

I suspect the problem is related to this one:

Quote from: jmone on August 07, 2013, 06:01:24 am

- There is an Application Error logged by MC saying "Windows cannot access the file..."

This shows up in my system logs as well, around the same time that MC crashes.

bulldogger · « **Reply #28 on:** August 07, 2013, 07:54:35 pm »

Quote from: JimH on August 05, 2013, 09:33:10 am

Including 18.0.211?

Same issue. Latest build also crashing. I am importing a large library but never get past about 36 hours before it crashes. Sent logs twice to help.

pqcgebxm · « **Reply #29 on:** August 08, 2013, 03:51:07 am »

Quote from: bulldogger on August 07, 2013, 07:54:35 pm

Same issue. Latest build also crashing. I am importing a large library but never get past about 36 hours before it crashes. Sent logs twice to help.

This may not be the same issue. Are you saying that it crashes while you're importing files? The others in this thread are experiencing crashes while *idle*. You might want to start a new thread.

jmone · « **Reply #30 on:** August 08, 2013, 03:56:42 am »

Yup, this thread is about OLE32 related crashes

pqcgebxm · « **Reply #31 on:** August 08, 2013, 04:02:05 am »

Another crash today. I've noticed something that might be useful:

At 4:21:59 PM I got these two final log messages from MC before it crashed (these are the same ones as previously reported... skip past these two to see what might be interesting):

1) Faulting application name: Media Center 18.exe, version: 18.0.212.0, time stamp: 0x51ffbb75
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96f
Exception code: 0xc0000096
Fault offset: 0x00048665
Faulting process id: 0x1768
Faulting application start time: 0x01ce92ef1f2d24a1
Faulting application path: C:\Program Files (x86)\J River\Media Center 18\Media Center 18.exe
Faulting module path: C:\Windows\syswow64\ole32.dll
Report Id: d47c5924-fff2-11e2-af88-3c07540350e3

2) Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Media Center 18 because of this error.

Program: Media Center 18
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

But, at the same time (4:21:59), I also received six separate system log messages identical to this, and I noticed that this seemed to occur at the same time as the above error messages on the previous day:

Log Name: System
Source: amdkmdag
Date: 8/08/2013 4:21:59 PM
Event ID: 62464
Task Category: DVD_OV
Level: Information
Keywords: Classic
User: N/A
Computer: MediaPC
Description:
UVD Information
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="amdkmdag" />
<EventID Qualifiers="16384">62464</EventID>
<Level>4</Level>
<Task>61</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-08T06:21:59.762378200Z" />
<EventRecordID>413854</EventRecordID>
<Channel>System</Channel>
<Computer>MediaPC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00006000010000003D00000000F4004000000000000000000000000000000000000000000000000 0FFFFFFFF0005064C03000000030000000000000003000000030000000000000003000000030000 00000000000300000000000000000000000300000000000000000000000005040000803E003C000 0000000000000803E003C00000000000000</Binary>
</EventData>
</Event>

pqcgebxm · « **Reply #32 on:** August 08, 2013, 05:13:03 am »

Quote from: Sinnerman on August 08, 2013, 04:02:05 am

But, at the same time (4:21:59), I also received six separate system log messages identical to this, and I noticed that this seemed to occur at the same time as the above error messages on the previous day:

Hmmmm... This was probably a red-herring. Apparently, it's just spam log notifications from the video driver:

http://www.nooblet.org/blog/2011/suppress-eventviewer-ati-amdkmdag-spam/

But, the first two error messages from MC do seem to be relevant, or at least they regularly appear in the logs. Has anyone else who is experiencing this problem seen these messages in the Windows event viewer?

Matt · « **Reply #33 on:** August 08, 2013, 08:47:05 am »

Quote from: bulldogger on August 07, 2013, 07:54:35 pm

Same issue. Latest build also crashing. I am importing a large library but never get past about 36 hours before it crashes. Sent logs twice to help.

Your log shows a problem parsing this file:
F:\DSDISO folder\DSDISO folder\Bon Jovi - This Left Feels Right.iso

What happens if you manually drag-n-drop that file into MC?

If it hangs, could you provide a sample of the file using Dropbox?

Thanks.

bulldogger · « **Reply #34 on:** August 08, 2013, 02:59:24 pm »

Quote from: Matt on August 08, 2013, 08:47:05 am

Your log shows a problem parsing this file:
F:\DSDISO folder\DSDISO folder\Bon Jovi - This Left Feels Right.iso

What happens if you manually drag-n-drop that file into MC?

If it hangs, could you provide a sample of the file using Dropbox?

Thanks.

File works fine.

pqcgebxm · « **Reply #35 on:** August 08, 2013, 09:50:00 pm »

Does anyone have any theories on whether either of these two log entries are related? These are the two that always seem to occur together, and are the last ones in the Windows application log before MC crashes (though I can't say if they occur at the same time of the crash). What about the second one, especially? It says that a file could not be accessed, but the path for the file is blank.

1) Faulting application name: Media Center 18.exe, version: 18.0.212.0, time stamp: 0x51ffbb75
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96f
Exception code: 0xc0000096
Fault offset: 0x00048665
Faulting process id: 0x1768
Faulting application start time: 0x01ce92ef1f2d24a1
Faulting application path: C:\Program Files (x86)\J River\Media Center 18\Media Center 18.exe
Faulting module path: C:\Windows\syswow64\ole32.dll
Report Id: d47c5924-fff2-11e2-af88-3c07540350e3

2) Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Media Center 18 because of this error.

Program: Media Center 18
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

jmone · « **Reply #36 on:** August 08, 2013, 11:07:50 pm »

Quote

Does anyone have any theories on whether either of these two log entries are related?

They were for me. In fact I had three that always occurred in a single group lasting only a couple of seconds at most. These two report + one that seemed to be a network event "waking" up my HTPC (from my backup server).

Matt · « **Reply #37 on:** August 09, 2013, 09:07:03 am »

Quote from: bulldogger on August 08, 2013, 02:59:24 pm

File works fine.

If the file works fine, that means it's probably not the issue.

I wonder if you might split your import into small parts. Do a few folders, restart MC, do a few more.

If you find a folder that reliably crashes, we'll get a few more logs.

Thanks for your help.

(ps. Once I know you've seen this, I may split this discussion to a new thread with bulldogger in the subject. I don't believe your problem is related to the COM issue others are having in this thread.)

bulldogger · « **Reply #38 on:** August 09, 2013, 07:48:11 pm »

Oh, I have also had the randomly crashes while idle problem. In fact, just as I type this!, it just crashed while idle, no importing. That's why I posted on this thread. I assumed that the problem my not be related to just importing as it was crashing just while idle. I will send that log as well.

hooli · « **Reply #39 on:** August 09, 2013, 08:35:29 pm »

Here is my most recent crash log. Running Windows 7 x64. Bitdefender Internet Security. I have woken up to a crash notification every morning.

bulldogger · « **Reply #40 on:** August 10, 2013, 04:46:15 am »

I uninstalled JRiver and then reinstalled. So far, it has not crashed and I am back to importing files. It had started crashing so much that I saw no other option but to reinstall it.

pqcgebxm · « **Reply #41 on:** August 10, 2013, 06:44:30 pm »

Quote from: Matt on August 05, 2013, 09:56:42 am

If you find any extra clues, please share.

I've provided a few extra logs, etc. Is any of this useful? Is there something specific I should provide?

justsomeguy · « **Reply #42 on:** August 13, 2013, 06:36:32 pm »

Just an update, I still have not had a crash since making the change matt suggested to the tv guide downloading. Sounds like other are having bigger problems than that though. I hope it gets resolved for everybody but for now my problem seems to be resolved.

now I'm off to install MC19

Thanks

pqcgebxm · « **Reply #43 on:** August 13, 2013, 07:52:33 pm »

Quote from: bulldogger on August 10, 2013, 04:46:15 am

I uninstalled JRiver and then reinstalled. So far, it has not crashed and I am back to importing files. It had started crashing so much that I saw no other option but to reinstall it.

Are you still crash-free?

When you re-installed, did you first uninstall the previous version? I've installed new versions without uninstalling the previous one many times, but that has not resolved this issue.

pqcgebxm · « **Reply #44 on:** August 27, 2013, 03:15:53 am »

This just happened for this first time while I was actually playing music. The music suddenly started stuttering, and the crash dialog appeared with the same ole32 crash message. I've attached my MC log.

Does this provide any additional clues?

Matt · « **Reply #45 on:** August 30, 2013, 02:59:29 pm »

Quote from: Sinnerman on August 27, 2013, 03:15:53 am

This just happened for this first time while I was actually playing music. The music suddenly started stuttering, and the crash dialog appeared with the same ole32 crash message. I've attached my MC log.

Does this provide any additional clues?

Unfortunately this is still a mystery to us.

However, we're making some structural changes in MC 19.0.34 with regards to COM usage hoping it might help.

Maybe you could test it once it's available next week?

Thanks.

bulldogger · « **Reply #46 on:** August 31, 2013, 07:07:41 am »

Quote from: Sinnerman on August 13, 2013, 07:52:33 pm

Are you still crash-free?

When you re-installed, did you first uninstall the previous version? I've installed new versions without uninstalling the previous one many times, but that has not resolved this issue.

It worked for awhile but then crashed again. I uninstalled the previous version. I repeated the process and have been crash free once again.

pqcgebxm · « **Reply #47 on:** September 03, 2013, 08:03:09 pm »

Quote from: Matt on August 30, 2013, 02:59:29 pm

Unfortunately this is still a mystery to us.

However, we're making some structural changes in MC 19.0.34 with regards to COM usage hoping it might help.

Maybe you could test it once it's available next week?

Unfortunately, this made no difference. I've been running 19.0.32 for a few days now, and it crashes just like v18.

One thing I have noticed: it only seems to crash if the client is running. If only the server is running, then it's ok.

Matt · « **Reply #48 on:** September 03, 2013, 11:02:58 pm »

Quote from: Sinnerman on September 03, 2013, 08:03:09 pm

Unfortunately, this made no difference. I've been running 19.0.32 for a few days now, and it crashes just like v18.

Please note that I said 19.0.34. It may be public later this week, depending on how testing goes.

pqcgebxm · « **Reply #49 on:** September 03, 2013, 11:10:51 pm »

Quote from: Matt on September 03, 2013, 11:02:58 pm

Please note that I said 19.0.34. It may be public later this week, depending on how testing goes.

Ah! My mistake -- I thought you were referring to the stable release of v19. Ok, I'll test again when .34 is released.

INTERACT FORUM

Author Topic: Randomly crashing while idle (Read 8670 times)