• 1
  • 7
  • 8
  • 9(current)
  • 10
  • 11
  • 12
Win Error: unable to create application. Exiting
Thx very much for your detailled analysis on the bugtracker: I hope to get a wait max 30 seconds into Helix: https://github.com/xbmc/xbmc/pull/6659 - I think it's quite unlikely to have more than 15 sound devices.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Here is the mentioned testbuild: http://mirrors.xbmc.org/test-builds/win3...ease20.exe
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Awesome, thanks @fritsch. Although, it does seem that some folks actually do have 15+ audio devices if they use their system for audio production as well - see post http://forum.kodi.tv/showthread.php?tid=...pid1941272 in this thread for one case. I'm guessing that for @Zytrel diabling audio devices to get below the timeout wouldn't be such a great workaround... That being said, it should at least address the majority of users' issues. Maybe we can at least add a warning if more than 15 audio devies are detected that startup will likely time out? Or we set a timeout of # of devies * 2.1s (don't know if the list or number of devices is available before initialization, of course - although it does seem to be able to spit out the whole list even when timing out)?
Reply
The majority of users (currently some millions) could live very good with the 10 seconds we had :-). Problem here is, that the init does not yet know about how many devices we have ... therefore it cannot dynamically wait. There is another problem: If users without audio devices tried to start kodi - they would not see anything for 60 seconds and likely will do another double click.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Not sure if possible with our code and just a thought, but you could mimic dynamic wait by "resetting the timer" each time a device was found. Ofc there's a little chance to wait for ever.
Reply
That needs more code in the implementation of the state machine. As for now we only have sync and non sync messages with fixed timings.

I think: https://github.com/xbmc/xbmc/pull/6659#i...t-77811511 will tell us exactly why waiting needs that long time.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-03-08, 19:27)fritsch Wrote: Thx very much for your detailled analysis on the bugtracker: I hope to get a wait max 30 seconds into Helix: https://github.com/xbmc/xbmc/pull/6659 - I think it's quite unlikely to have more than 15 sound devices.

Not Unlikely for users who have added a high End Audio card to replace an onboard audio system.
That alone can be 6-8 devices right there then throw in any HDMI Audio devices and you are quickly at 10.
My issue may be related to a DRM removal tool that adds a bunch of Virtual Audio devices so it can do multiple Audio files at the same time.
Which is why I'm probably way over 15.
My HTPC is doing a lot more than just acting as an HTPC...
It also runs my Plex Server and does the majority of my Ripping, Encoding and Merging needed before I put stuff into my Library.
Which is why I have two Video Cards installed one for working on those media functions and one dedicated to XBMC output.

Also why I won't be whining anytime about this issue because in some small way it is my own doing. LOL
Reply
14.2 RC has been released. Has anyone tried it yet? Would we still need a special build for the "Unable to create" bug?
Reply
The workaround was pushed - so all is in that should make it work: https://github.com/xbmc/xbmc/commit/fd9b...bca69a5add
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-03-14, 08:57)fritsch Wrote: The workaround was pushed - so all is in that should make it work: https://github.com/xbmc/xbmc/commit/fd9b...bca69a5add

Awesome! Thanks, I will update Kodi as soon as I get home.
Reply
(2015-03-14, 08:57)fritsch Wrote: The workaround was pushed - so all is in that should make it work: https://github.com/xbmc/xbmc/commit/fd9b...bca69a5add

Thanks for all your help and hand holding through all of this!
Reply
Hi - out of the sudden I do have the same problem.

Since almost 2 years I am using XBMC / Kodi without any major issue. Since the day one, I am using V15 also without any major issue on several devices. However, today I started my computer (without modifying anything since I turned it off yesterday) the error message came up. Tried to install the V15 beta 1 again - no success. Tried to start the latest hightly (19 May) - no success :-( I can't try V14 because the mySQL server is also running V15...

I do have 3 audio devices and I didn't touch the drivers or changes anything related to the audio devices. So I am on the lost...

I thing I did yesterday - I deactivated the "Beck-up" Plug-in in Kodi - but I don't think it is related to this, isn't it ?
Reply
No idea ... continue speculating or consider posting a Debug Log
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
You're right- sorry.

However, I just inserted "<loglevel>2</loglevel>" in the advancedsettings.xlm, but the kodi.log in the Kodi folder (one folder above the userdata folder) file is just empty.
There are tow addionalfiles - xbmc_stacktrace.....txt and xbmx_crashlog....dmp.

The ...txt files are as follows:
Thread 988 (process 3488)
# 0
# 1
# 2
# 3
# 4
# 5 BaseThreadInitThunk
# 6 RtlInitializeExceptionChain
# 7 RtlInitializeExceptionChain
The thread number and process number chances with every attemp to start Kodi - the rest remains the same. The ...dmp file I can't read this file with an editor - what shall I do with this file ?
Reply
After a clean install of Kodi (uninstalled and deleted everthing first, then reinstall) Kodi is working again...
Reply
  • 1
  • 7
  • 8
  • 9(current)
  • 10
  • 11
  • 12

Logout Mark Read Team Forum Stats Members Help
Error: unable to create application. Exiting0