Opened 11 years ago

Closed 9 years ago

#3418 closed bug (invalid)

media_server crashes at startup with rev291524

Reported by: the ringmaster Owned by: marcusoverhagen
Priority: normal Milestone: R1
Component: Servers/media_server Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

here is a screenshot. I don't really know what other information I can give.

Attachments (1)

media_server.png (57.8 KB ) - added by the ringmaster 11 years ago.

Download all attachments as: .zip

Change History (11)

by the ringmaster, 11 years ago

Attachment: media_server.png added

comment:1 by mmlr, 11 years ago

You could additionally mention that it is a GCC4 build.

in reply to:  1 comment:2 by the ringmaster, 11 years ago

Replying to mmlr:

You could additionally mention that it is a GCC4 build.

yes it is a gcc 4 build, but I started haiku up again and media_server didn't crash. This might be invalid if no one else experiences this.

comment:3 by mmlr, 11 years ago

I've seen this as well on GCC4 builds, that's why I knew. It's not invalid, but as you say usually this doesn't happen on every boot.

comment:4 by leavengood, 10 years ago

I am getting this error on hrev31524 after updating everything for the 32-bit wchar_t change. Also this is on GCC 2.

Whenever I try to run the media_server the above error comes up and I see this in the serial log:

bfs: bfs_access:1428: Operation not allowed

comment:5 by leavengood, 10 years ago

On second thought, it seems this problem was probably due to my not completely deleting all old files before rebuilding ("jam clean" did not do the job.) So ignore my previous comment.

comment:6 by jackburton, 10 years ago

Can we close this ?

in reply to:  6 comment:7 by the ringmaster, 9 years ago

Replying to jackburton:

Can we close this ?

yes we can close this now

comment:8 by Disreali, 9 years ago

any reason to have this still open?

comment:9 by the ringmaster, 9 years ago

I don't think that this is a problem anymore. Please close it if no one else experiences this either.

comment:10 by marcusoverhagen, 9 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.