Opened 14 years ago
Closed 4 years ago
#6993 closed bug (fixed)
BeSting app doesn't work, causes crashes on shutdown and startup.
Reported by: | Meanwhile | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | Servers/media_server | Version: | R1/alpha2 |
Keywords: | BeSting | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
BeOS application BeSting http://haikuware.com/directory/view-details/multimedia/audio/recording/besting doesn't work in Haiku hrev39848. It causes high CPU activity when active, though.
The attached serial log (BeStingStartupPart1and2) hopefully gives some clues; the first part shows Haiku booting, second part (after the break) shows what happens when BeSting is activated. I had to shut down BeSting to stop the data.
When shutting down Haiku after that, there are two windows showing up (see attached photo): first the one on the left, then the one on the right.
On the following boot, Haiku crashes again (see attachment called HaikuCrashStartup).
Attachments (3)
Change History (10)
by , 14 years ago
Attachment: | BeStingStartupPart1and2 added |
---|
by , 14 years ago
Attachment: | P1000101b.jpg added |
---|
by , 14 years ago
Attachment: | HaikuCrashStartup added |
---|
comment:1 by , 13 years ago
Component: | Audio & Video → Servers/media_server |
---|---|
Owner: | changed from | to
comment:2 by , 10 years ago
comment:3 by , 10 years ago
Just tried it, works nicely. Though I had one crash when launching it for the first time. Didn't happen again. Here's the syslog part of it, JFYI:
KERN: vm_soft_fault: va 0x4af62000 not covered by area in address space KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x4af62bc1, ip 0x1c74aec, write 0, user 1, thread 0x87b KERN: vm_page_fault: thread "BeSting" (2171) in team "BeSting" (2171) tried to read address 0x4af62bc1, ip 0x1c74aec ("libbe.so_seg0ro" +0x1d5aec) KERN: debug_server: Thread 2171 entered the debugger: Segment violation KERN: stack trace, current PC 0x1c74aec RemoveSelf__5BView + 0x18: KERN: (0x7156945c) 0xfef034 FillMidiOutputList__12BeStingCtrls + 0x30 KERN: (0x715694ec) 0xfee9ae __12BeStingCtrlsP13BeStingPlayer + 0x137a KERN: (0x71569668) 0xfed1ea __10BeStingApp + 0xaa KERN: (0x715696a8) 0xfed0b2 main + 0x22 KERN: (0x715697cc) 0xfea435 _start + 0x61 KERN: (0x715697f8) 0xb52acc runtime_loader + 0x134 KERN: acpi: Notify event 129 for \_SB_.BAT0 Last message repeated 2 times KERN: debug_server: Killing team 2171 (/HiQ-Data/downloads/BeSting/BeSting) KERN: debug_server: TeamDebugHandler::Init(): Failed to get info for team 2171: Operation on invalid team KERN: debug_server: KillTeam(): Error getting info for team 2171: Operation on invalid team KERN: debug_server: Killing team 2171 ()
comment:4 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:6 by , 4 years ago
It's on the web archive: http://web.archive.org/web/20120622061449/http://www.benloftis.com/software
Seems to crash as humdinger says, but not just the first time for me.
comment:7 by , 4 years ago
Milestone: | R1 → R1/beta2 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Well, besides that problem at start which is a bug in the app (race condition, it tries to call RemoveSelf on a not-yet-initialized pointer to a view, apparently), it seems the original bug is gone indeed.
Works fine here, can anyone reproduce this?