
|
[openbeosmediakit]
||
[Date Prev]
[07-2003 Date Index]
[Date Next]
||
[Thread Prev]
[07-2003 Thread Index]
[Thread Next]
[openbeosmediakit] GUI problems
- From: "Marcus Overhagen" <ml@xxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Wed, 02 Jul 2003 01:46:30 GMT
Hi,
I'm currently implementing the new system audio mixer,
and some of the advanced controls require creation
of a lot of small sliders (about 40 for each input or output).
This is done by creating parameter controls of type
BContinuousParameter, which are then drawn by the media
kit using standard interface kit classes like BSlider.
However, this is a huge problem, since BeOS will
run out of memory when creating more then about
130 sliders.
The results are very ugly, since applications will freeze, and
the syslog will show things like:
KERN 'AppKit'[39]: find_virtual_space2 : out of virtual space (base:
0xfc000000, size: 00040000)!
KERN 'AppKit'[39]: create_area_gen error -1 (0xfc000000, 2, 16)
KERN 'AppKit'[39]: find_virtual_space2 : out of virtual space (base:
0xfc000000, size: 00040000)!
KERN 'AppKit'[39]: find_virtual_space2 : out of virtual space (base:
0xfc000000, size: 00040000)!
KERN 'AppKit'[39]: create_area_gen error -1 (0xfc000000, 2, 16)
KERN 'a:Media:2143'[17694]: stateStack non-null!
Obviously, app_server create a huge number of threads when there controls are
created,
and runs out of stack space (every thread uses 256 kB)
1. What is the source of this limit, what are all the threads used for?
2. We must(!!!) be able to create more sliders, perhaps 10000 or more.
3. Comments?
Marcus
|

|