Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FB custom sometimes enters infinite memory allocation loop #164

Closed
ohrrpgce-bugbot opened this issue Mar 2, 2006 · 7 comments
Closed

FB custom sometimes enters infinite memory allocation loop #164

ohrrpgce-bugbot opened this issue Mar 2, 2006 · 7 comments
Labels
bug Yeah... that's broken Custom General problems; use "editor UI" for editor issues rel: tirgoviste Present in tirgoviste 2006-03-15 resolved: works for me Couldn't be reproduced or disappeared on its own

Comments

@ohrrpgce-bugbot
Copy link

[bz#164]

(These may be one of those bugs that only one person ever experience)

Haggard complained today that very often and at completely random times FBCustom
freezes - he said this happened every few minutes and had happened both while
pixelating and setting hero stats for example. He also said:

just freeze
and it eats up y ram, i think
i get the low virtual memory message

He tried both S+ and nightly fb2-native builds. On switching to any of the
allegro gfx builds, the problem went away.

From: @rversteegen
Reported version: 20060315 Tirgoviste
Operating system: Windows XP
@ohrrpgce-bugbot
Copy link
Author

Comment author: Simon Bradley <neworiginal>

There was a problem with the flood fill doing exactly that when you filled an
area with the colour it already was, but it should be fixed in the nightly build
and wouldn't have worked any differently in Allegro.

@ohrrpgce-bugbot
Copy link
Author

Comment author: @rversteegen

PS: I was confused, it was Slime who reported this. All due to Haggard's
frequent nick-switching.

@ohrrpgce-bugbot
Copy link
Author

Comment author: @bob-the-hamster

Is this bug still reproducable?
I am guessing that this was related to bug bz⁠#163, maybe?

@ohrrpgce-bugbot
Copy link
Author

Comment author: @rversteegen

I highly doubt it is. Possibly it never happened. I vote to close. However,
there are plenty of other crash bugs that could use reports (I can think of one,
which I'll file once I get some better reproducability)

@ohrrpgce-bugbot
Copy link
Author

Comment author: @rversteegen

I'm closing this. The reporter even told me he can't even access the computer he
might have seen it on anymore (fried or something)

@ohrrpgce-bugbot
Copy link
Author

Comment author: @pkmnfrk

For wholly unrelated reasons, right?

@ohrrpgce-bugbot
Copy link
Author

Comment author: @pkmnfrk

Wrong answer, but I'll pretend you said "no".

@ohrrpgce-bugbot ohrrpgce-bugbot added Custom General problems; use "editor UI" for editor issues resolved: works for me Couldn't be reproduced or disappeared on its own bug Yeah... that's broken rel: tirgoviste Present in tirgoviste 2006-03-15 labels Mar 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Yeah... that's broken Custom General problems; use "editor UI" for editor issues rel: tirgoviste Present in tirgoviste 2006-03-15 resolved: works for me Couldn't be reproduced or disappeared on its own
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ohrrpgce-bugbot