Jump to content


Photo

Crash on F2 open browser


5 replies to this topic

#1 Gogalthorp

Gogalthorp

    White Rabbit

  • Members
  • 39 posts

Posted 08 May 2015 - 04:36 PM

openSUSE 13.2 FireFox browser

 

running from the command line and pressing F2 with a URL in play this is the error

 

gogalthorp@linux:~/eternallands> ./eternallands.sh
(process:7130): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Assertion 'pa_atomic_load(&(B)->_ref) > 0' failed at pulsecore/memblock.c:597, function pa_memblock_unref(). Aborting.
./eternallands.sh: line 39:  7114 Aborted                 $(which padsp) ./el.*.linux.bin $server
 

 

Note the setup is the same as previous version with browser noted as firefox.


(B)  is  ( b )  no spaces

 



#2 bluap

bluap

    Feran

  • Moderators
  • 2219 posts
  • Gender:Male
  • Location:UK

Posted 08 May 2015 - 08:03 PM

This is already under investigation, see this thread. Alternative, Burn has make Suse packages.



#3 revi

revi

    Skeleton

  • Moderators
  • 1022 posts
  • Gender:Not Telling

Posted 08 May 2015 - 08:08 PM

For what it's worth, the 'GLib-CRITICAL' message is caused by Firefox (afaik, some other programs might be causing it as well) and has nothing to do with the EL client.

 

I'm using OpenSuse 13.2 and an EL client compiled from GIT (pull and compile from this afternoon, say 8h ago) and that's running w/o any glitches so far (specifically, F2 does not cause a crash, but opens a tab in firefox as expected). Also sound works as usual.



#4 Gogalthorp

Gogalthorp

    White Rabbit

  • Members
  • 39 posts

Posted 08 May 2015 - 11:03 PM

Well FF starts and EL crashes. Note Ihad no problem on the previous version

 

Might need to pull from git but let's see if we get a general update. I can live without the F2 for a while. And in any case the program should not crash on a chain to another program.



#5 bluap

bluap

    Feran

  • Moderators
  • 2219 posts
  • Gender:Male
  • Location:UK

Posted 08 May 2015 - 11:14 PM

Its only the static build that has this problem.  Building your own would work fine.  Before the server update, I had time to test the 193 version too, that crashed in the same way.  If you turn sound & music off before opening the URL then the client does not crash.  I'm going to use that as a work around for now (switching off/on as required) and build a new static binary.



#6 bluap

bluap

    Feran

  • Moderators
  • 2219 posts
  • Gender:Male
  • Location:UK

Posted 09 May 2015 - 12:31 PM

New builds with the work around are available, see here.





Reply to this topic



  


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users