Had a quick look at the forums, couldn't see a specific bug report section (maybe I'm blind)
Fast forwarding a file on a Samba share (Windows host) by using the "arrow left and right" button for 30 second skips.
Hit it up for about 30 skips in a row quite quickly and over she went, crashed.
Faulting application name: XBMC.exe, version: 10.5.0.0, time stamp: 0x4f4ef4a9
Faulting module name: XBMC.exe, version: 10.5.0.0, time stamp: 0x4f4ef4a9
Exception code: 0xc0000409
Fault offset: 0x007f8d29
Faulting process id: 0x23cc
Faulting application start time: 0x01cd08d2a3e0f84f
Faulting application path: C:\Program Files (x86)\XBMC\XBMC.exe
Faulting module path: C:\Program Files (x86)\XBMC\XBMC.exe
Report Id: 995ba716-74d6-11e1-8b42-005056c00008
Mind you, I was using the Android XBMC remote, unsure if this influenced the crash.
Running on Windows 7 64bit, fully patched with an ATI card. 2560x1600 - playing back ST:TOS episode in the 500mb range.
Try it without the android remote. As all my files are on SMB shares and I use the "up" skip all the time without issue. Also grabbing a
debug log would be helpful.
(2012-03-23, 13:00)AbRASiON Wrote: [ -> ]Hit it up for about 30 skips in a row quite quickly and over she went, crashed.
Thought you were still playing the XBox?
(2012-03-23, 13:00)AbRASiON Wrote: [ -> ]Running on Windows 7 64bit, fully patched with an ATI card. 2560x1600 - playing back ST:TOS episode in the 500mb range.
Windows 7x64 with nVidia ION here (Acer Revo 3700) with exactly the same problem since the Eden betas - unfortunately I've not been able to consistently reproduce and you can guarantee the day after I disable debug logging I get another crash. Not noticed it happening when skipping with 'up/down' but if I skip with 'left/right' a bunch (normally when trying to find my spot in a movie i've been watching elsewhere) I get a crash - felt like it happened more often after resuming from suspend but I have no proof of that,
Well in the next 9 days XBMC is going to become my primary player in the loungeroom so I guess I'll be updating this thread significantly more then.
(2012-03-23, 18:13)DDDamian Wrote: [ -> ] (2012-03-23, 13:00)AbRASiON Wrote: [ -> ]Hit it up for about 30 skips in a row quite quickly and over she went, crashed.
Thought you were still playing the XBox?
Well, look at my registration date
I mean I was using this thing since it was Xbox Meda Player (I think that's the name, it's been a while)
(2012-03-24, 12:11)AbRASiON Wrote: [ -> ] (2012-03-23, 18:13)DDDamian Wrote: [ -> ] (2012-03-23, 13:00)AbRASiON Wrote: [ -> ]Hit it up for about 30 skips in a row quite quickly and over she went, crashed.
Thought you were still playing the XBox?
Well, look at my registration date I mean I was using this thing since it was Xbox Meda Player (I think that's the name, it's been a while)
I see that - naw just couldn't resist the button-mashing comment.
Faulting application name: XBMC.exe, version: 10.5.0.0, time stamp: 0x4f6a5a0a
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x1b5c
Faulting application start time: 0x01cd10c1d3d3c482
Faulting application path: C:\Program Files (x86)\XBMC\XBMC.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 90d2539c-7ccc-11e1-bf54-005056c00008
Faulting application name: XBMC.exe, version: 10.5.0.0, time stamp: 0x4f6a5a0a
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x25a0
Faulting application start time: 0x01cd10068a4c59d8
Faulting application path: C:\Program Files (x86)\XBMC\XBMC.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: d83bedb1-7bf9-11e1-bf54-005056c00008
Not using Android remote, machine is obscenely reliable the rest of the time.
Seems to be an intermittant issue MOST easily replicated by opening XBMC fresh and going to a new file, then skipping ahead manually (with the mouse) on the file.
EDIT: Also interesting, XBMC is repoirting itself as 10.5 in the event viewer, this is actually 11.
Whenever I click smallstepback (7s) several times rapidly or the 30s forward jump button XBMC crashes.
This is the windows event log:
Faulting application name: XBMC.exe, version: 10.5.0.0, time stamp: 0x4f6a5a0a
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x17d8
Faulting application start time: 0x01cd13555080077a
Faulting application path: C:\Program Files (x86)\XBMC\XBMC.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: b3c3fced-7f4e-11e1-aa14-50e5493a4e54
This is the end of my debug log (xbmc.log):
01:39:38 T:4792 DEBUG: CDVDPlayer::SetCaching - caching state 0
01:39:38 T:4792 DEBUG: CDVDPlayer::CheckPlayerInit - dropping packet type:2 dts:510927083.333333 to get to start point at 511000000.000000
01:39:38 T:4792 DEBUG: CDVDPlayer::CheckPlayerInit - dropping packet type:2 dts:510968791.666667 to get to start point at 511000000.000000
01:39:38 T:2492 DEBUG: CDVDPlayerAudio:: Discontinuity - was:511010894.065792, should be:511011014.417367, error:120.351575
01:39:38 T:2492 DEBUG: CWin32DirectSound::CheckPlayStatus: Resuming Playback
01:39:38 T:5668 DEBUG: SDLKeyboard: scancode: 4b, sym: 0114, unicode: 0000, modifier: 0
01:39:38 T:5668 DEBUG: CApplication::OnKey: left (f082) pressed, action is SmallStepBack
01:39:38 T:4792 DEBUG: CDVDPlayer::SetCaching - caching state 2
01:39:38 T:4792 DEBUG: demuxer seek to: 504000
01:39:38 T:4792 DEBUG: CDVDDemuxFFmpeg::SeekTime - unknown position after seek
01:39:38 T:4792 DEBUG: demuxer seek to: 504000, success
01:39:39 T:2492 DEBUG: CDVDPlayerAudio - CDVDMsg::GENERAL_SYNCHRONIZE
01:39:39 T:4136 DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_SYNCHRONIZE
01:39:39 T:4136 DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_RESYNC(511010500.000000, 0)
01:39:39 T:5668 DEBUG: CAnnouncementManager - Announcement: OnSeek from xbmc
01:39:39 T:5668 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnSeek
01:39:39 T:5668 DEBUG: SDLKeyboard: scancode: 4b, sym: 0114, unicode: 0000, modifier: 0
01:39:39 T:5668 DEBUG: CApplication::OnKey: left (f082) pressed, action is SmallStepBack
01:39:39 T:5668 DEBUG: CAnnouncementManager - Announcement: OnSeek from xbmc
01:39:39 T:5668 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnSeek
01:39:39 T:5668 DEBUG: SDLKeyboard: scancode: 4b, sym: 0114, unicode: 0000, modifier: 0
01:39:39 T:5668 DEBUG: CApplication::OnKey: left (f082) pressed, action is SmallStepBack
01:39:39 T:5668 DEBUG: CAnnouncementManager - Announcement: OnSeek from xbmc
01:39:39 T:5668 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnSeek
01:39:39 T:5668 DEBUG: SDLKeyboard: scancode: 4b, sym: 0114, unicode: 0000, modifier: 0
01:39:39 T:5668 DEBUG: CApplication::OnKey: left (f082) pressed, action is SmallStepBack
01:39:39 T:5668 DEBUG: CAnnouncementManager - Announcement: OnSeek from xbmc
01:39:39 T:5668 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnSeek
01:39:40 T:4136 DEBUG: CPullupCorrection: detected pattern of length 1: 41708.33, frameduration: 41708.333333
01:39:47 T:124 DEBUG: Thread Jobworker 124 terminating (autodelete)
01:39:47 T:6608 DEBUG: Thread Jobworker 6608 terminating (autodelete)
01:39:47 T:2196 DEBUG: Thread Jobworker 2196 terminating (autodelete)
Can someone with this issue post a full log with debugging turned on?
Can we also get your settings used in system\video output, system\audio output and video\playback? The more info we have the better. I have not been able to replicate this on 3 different Windows PCs.
Extremely intermittant problem - happens maybe once every 2 days so the logs would be mammoth - but if it continues, I'll certainly turn logging on.
Tried turning debugging on, but am unable to reproduce the problem for now. Will turn it on again if it starts occurring again.
Not sure if it's related but I just upgraded my nVidia display drivers. see if that's related/helps...
by the way, I have no idea if it's relevant but I am using the Motorola Nyxboard remote.
I've had problem primarily on my desktop PC (ATI)