boxee box support? boxee keeps rebooting

[Ozpeter]

So if you need to use UPnP to access your media the way you want, what do you do? Go without I guess. I hope this is due for an early fix...

[joesavage]

I don't think ALL UPnP sources are problematic, in fact after I disabled UPnP on the device that was causing my problem, I re-enabled it on my Windows 7 computers and it hasn't caused any problems.

After reproducing the problem on Boxee for Windows, I built the windows version from source and caught the crash in the debugger (and saw the exact same call stack as in the boxee box log). This gave me enough information to tell which device was causing the problem.

I expect that the developers are quite busy now trying to get the netflix support released, and once they do they will address this issue.

[larryd2910]

does anyone still have this problem even with upnp disabled on NAS-323 and router linksys E2000 ?

[joesavage]

Larry, did you take a look at the root-boxee.log file from the box's crash report? Just curious if this is the same problem or something else.

If you haven't looked at the report, try this:
* Ensure that the debug output is enabled on the boxee box (Settings->System->Advanced->Debug Level = INFO)
* Wait for a crash
* On your computer browser, go to http://[boxeebox ip address]:8080
* Download one of the error logs (it's a *.bz2 file)
* Open this file with WinRAR or 7-Zip
* Look at the root-boxee.log file with a text editor

In the root-boxee.log file, look for the words "Stack trace (faulting thread)" and if you see the same thing as in my post above, I am willing to bet that you still have UPnP enabled on some device on your network. In the case with my Linksys NAS200, I had to disable it in two places on the NAS200 configuration web page.

Good luck,
Joe

[larryd2910]

Larry, did you take a look at the root-boxee.log file from the box's crash report? Just curious if this is the same problem or something else.

If you haven't looked at the report, try this:
* Ensure that the debug output is enabled on the boxee box (Settings->System->Advanced->Debug Level = INFO)
* Wait for a crash
* On your computer browser, go to http://[boxeebox ip address]:8080
* Download one of the error logs (it's a *.bz2 file)
* Open this file with WinRAR or 7-Zip
* Look at the root-boxee.log file with a text editor

In the root-boxee.log file, look for the words "Stack trace (faulting thread)" and if you see the same thing as in my post above, I am willing to bet that you still have UPnP enabled on some device on your network. In the case with my Linksys NAS200, I had to disable it in two places on the NAS200 configuration web page.

Good luck,
Joe

Thanks joe i'll try and wait for a crash

[larryd2910]

Larry, did you take a look at the root-boxee.log file from the box's crash report? Just curious if this is the same problem or something else.

If you haven't looked at the report, try this:
* Ensure that the debug output is enabled on the boxee box (Settings->System->Advanced->Debug Level = INFO)
* Wait for a crash
* On your computer browser, go to http://[boxeebox ip address]:8080
* Download one of the error logs (it's a *.bz2 file)
* Open this file with WinRAR or 7-Zip
* Look at the root-boxee.log file with a text editor

In the root-boxee.log file, look for the words "Stack trace (faulting thread)" and if you see the same thing as in my post above, I am willing to bet that you still have UPnP enabled on some device on your network. In the case with my Linksys NAS200, I had to disable it in two places on the NAS200 configuration web page.

Good luck,
Joe

Didn't have to wait too long :Here is what I got don't know if it's enough:

Stack trace (faulting thread):

1: 0x8bb0364 <CRarManager::CacheRarredFile(CStdStr<char>&, CStdStr<char> const&, CStdStr<char> const&, unsigned char, CStdStr<char> const&, long long)+2224> (./Boxee)

2: 0x8b62805 <XFILE::CFileRar::Open(CURL const&)+705> (./Boxee)

3: 0x8b60e29 <XFILE::CFileRar::Stat(CURL const&, stat64*)+33> (./Boxee)

4: 0x8b4a3ca <XFILE::CFile::Stat(CStdStr<char> const&, stat64*)+60> (./Boxee)

5: 0x87649d2 <CMetadataResolverVideo::GetFileData(std::string const&, long long&, int&)+100> (./Boxee)

6: 0x876620d <CVideoFileContext::LoadFileData()+65> (./Boxee)

7: 0x876e5bb <CVideoFileContext::Load(CStdStr<char> const&)+99> (./Boxee)

8: 0x8760093 <CMetadataResolver::ResolveVideoFolder(BOXEE::BXMe tadataScannerJob*)+1997> (./Boxee)

9: 0x87624f9 <CMetadataResolver::Resolve(BOXEE::BXMetadataScann erJob*, std::vector<BOXEE::BXFolder*, std::allocator<BOXEE::BXFolder*> >&)+731> (./Boxee)

10: 0x8e41ae5 <BOXEE::BXMetadataEngine::Resolve(BOXEE::BXMetadat aScannerJob*)+331> (./Boxee)

11: 0x8e41eab <BOXEE::BXMetadataScannerJob:oWork()+121> (./Boxee)

12: 0x8e19b14 <BOXEE::BXBGProcess::WorkerThread(void*)+640> (./Boxee)

13: 0x8e19b67 <BOXEE::BXBGProcess::WorkerPThread(void*)+17> (./Boxee)

14: 0xb7efa85c <(null)+3085936732> (system/bxwrapper.so)

15: 0xb7dd4151 <(null)+3084730705> (/lib/libpthread.so.0)

[joesavage]

OK Larry, I don't think your crash is due to UPnP.

From what I can tell by the stack trace, the crash comes when Boxee is scanning a folder that contains a RAR file. Perhaps there is a RAR file on your NAS that is corrupted and that is crashing Boxee. From just the stack trace I can't tell the file name, but maybe elsewhere in the debug log there is a hint of which file is being processed.

Good luck,
Joe

[stevefurey]

Hey Guys,

I was having the same problem, with the same stack trace. I had hundreds of RAR files which contained subtitles. I went through my media, extracted the subtitle and deleted the RAR files.

the box is sitting idle for hours in debug mode without a crash, something I've never been able to do.

I'm hoping this fixes it for me, just thought I'd share.