dMZX Forums: Intermittent crash when attempting to edit Global Robot -> MegaZeux Bugs -> Tracker

Jump to content

Report ID 719 Title Intermittent crash when attempting to edit Global Robot
Product MegaZeux Bugs Status UNFILED (Severity 0 - None Assigned)
Version 2.91e Fixed in -
Introduced In Version ----Operating System Windows 10 x64

Page 1 of 1
  • Cannot start a new Issue
  • You cannot reply to this issue

Report ID #719: Intermittent crash when attempting to edit Global Robot

#1 User is offline  
GetDizzy 

  • Touch Fuzzy.
  • Group: DigiStaff
  • Posts: 3,567
  • Joined: 22-November 01
  • Gender:Other
  • Location:MA

Posted 05 September 2018 - 06:21 AM

[2:12 AM] Insidious: ... that was bizarre
[2:12 AM] Insidious: megazeux just crashed when I was trying to go in to edit the global robot
[2:12 AM] Insidious: no idea what I did
[2:13 AM] Insidious: ... yeah if I load the backup of that world megazeux immediately quits.
[2:13 AM] Insidious: Lachesis: Want the world file?
[2:15 AM] Insidious: ... and it doesn't repro in gdb
[2:17 AM] Insidious: yeah I can get it repro somewhat reliably by repeatedly attempting to load the file and then edit the global robot, it doesn't happen every time. but I can't get it to happen with gdb.
[2:17 AM] Insidious: reporting the bug

Sorry I can't really give any more useful info than that. My laptop was a little low on RAM at the time, is the best guess I have for even vaguely useful info.

Here's the file
http://www.somebodye...ssiblecrash.mzx
- Your Jumpy Neighborhood Admin

<@Tixus> Anyway, I set the year to 1988 for some reason.
<@Tixus> And set the microwave to run for a minute and 28 seconds.
<@Tixus> But it failed to send me back in time, and I was disappointed.
<Insidious> Tixus accidentally microwaved the 80s
<Insidious> that is my takeaway from this


Page 1 of 1  
  • Cannot start a new Issue
  • You cannot reply to this issue

Replies (1 - 1)

#2 User is online  
Lachesis 

  • the pinnacle of human emotion
  • Group: DigiStaff
  • Posts: 3,904
  • Joined: 17-July 04
  • Gender:Female
  • Location:Sealand

Posted 05 September 2018 - 06:57 AM

This sounds like either something is not using the check_alloc functions (which should catch this situation and give an error) or somehow there wasn't even enough memory for check_alloc to display a message (doesn't make sense, but...).
"Let's just say I'm a GOOD hacker, AND virus maker. I'm sure you wouldn't like to pay for another PC would you?"

xx̊y (OST) - HELLQUEST (OST) - Zeux I: Labyrinth of Zeux (OST) (DOS OST)
w/ Lancer-X and/or asgromo: Pandora's Gate - Thanatos Insignia - no True(n) - For Elise OST
MegaZeux: Online Help File - Keycode Guide - Joystick Guide - Official GIT Repository


Page 1 of 1
  • Cannot start a new Issue
  • You cannot reply to this issue

1 User(s) are reading this issue
1 Guests and 0 Anonymous Users


Powered by IP.Tracker 1.3.2 © 2024  IPS, Inc.