Crashes on BasicHome screen (1 Viewer)

[mortstar]

omg...someone actually resolved it? If true, then I can't wait to install the next SVN and test.

Yes - we found it. The crash happened when MP had to manage more than 1000 control conditions.
MisterD fixed it by increasing the hardcoded value (old xmbc code) and making sure that "known" objects are reused.

You guys are on fire!

The fixes and improvements are coming thick and fast.

This one obviously makes community skins much more useable day-in, day-out.

Thanks so much.

 

[infinite.loop]

Fix is confirmed to be working, mantis entry has been closed

Next public build will contain the changes.

 

[pilehave]

Fix is confirmed to be working, mantis entry has been closed

Next public build will contain the changes.

Is the SVN updated with these changes? If so, I'll compile my own version to test with.

 

[zeebee]

Thanks a lot for fixing this issue. Looking forward to the next public SVN release!

 

[damaster]

Excellent news that this has been resolved! Can't wait 'till 1.0.1 is released!

 

[Kossan]

GREAT NEWS! Thanks.

 

[damaster]

Fix is confirmed to be working, mantis entry has been closed

Next public build will contain the changes.

Is the SVN updated with these changes? If so, I'll compile my own version to test with.

No, current SVN tag in the repository is 22029 and this is fixed in rev 22056

 

[infinite.loop]

Fix is confirmed to be working, mantis entry has been closed

Next public build will contain the changes.

Is the SVN updated with these changes? If so, I'll compile my own version to test with.

No, current SVN tag in the repository is 22029 and this is fixed in rev 22056

svn on sourceforge is updated as soon as we release the next public svn build.

you can blame sourceforge for that, because automatic syncing is not possible.

 

[damaster]

Is the SVN updated with these changes? If so, I'll compile my own version to test with.

No, current SVN tag in the repository is 22029 and this is fixed in rev 22056

svn on sourceforge is updated as soon as we release the next public svn build.

you can blame sourceforge for that, because automatic syncing is not possible.

Can you tell me which files were modified to fix this issue? I'd like to patch my current install manually.

Thanks

 

[infinite.loop]

No, current SVN tag in the repository is 22029 and this is fixed in rev 22056

svn on sourceforge is updated as soon as we release the next public svn build.

you can blame sourceforge for that, because automatic syncing is not possible.

Can you tell me which files were modified to fix this issue? I'd like to patch my current install manually.

Thanks

Today is public-svn-build day.