Menu
▾
▴
flightgear-bugs
|
From: <fli...@go...> - 2013-09-09 22:10:50
|
Status: New Owner: ---- New issue 1192 by jarl.arn...@gmail.com: Menu: Debug --> Print Rendering Statistics --> Crash http://code.google.com/p/flightgear-bugs/issues/detail?id=1192 *What steps will reproduce the problem?* 1. Start FG 2. Select Debug --> Print Rendering Statistics 3. Crash *What is the expected output? What do you see instead?* Expected to see rendering statistics on screen. Sim froze and had to be manually closed instead. *Any output in the console (black window)?* Fatal error (std:exception): bad allocation This is the full output from starting FlightGear until it crashes. No internationalization settings specified in preferences.xml Enabling ATI viewport hack SKIPPING POI load on Windows ALC Error (sound manager): Invalid Enum at context creation. environment init KMA20 audio panel initialized KI266 dme indicator #0 initialized Electrical system initialized KAP140 power up Error in ground network. Failed to find first waypoint: 0 at ENGM Error in ground network. Failed to find first waypoint: 0 at ENGM Error in ground network. Failed to find first waypoint: 0 at ENBR Error in ground network. Failed to find first waypoint: 0 at ENCN Error in ground network. Failed to find first waypoint: 0 at ENGM Error in ground network. Failed to find first waypoint: 0 at ENGM Error in ground network. Failed to find first waypoint: 0 at ENGM Error in ground network. Failed to find first waypoint: 0 at ENGM Error in ground network. Failed to find first waypoint: 0 at ENBR Fatal error (std::exception): bad allocation *What FlightGear version are you using (when using GIT version, please mention date)?* http://fgfs.goneabitbursar.com/releases/ fgsetup-2.12.0.exe 05-Sep-2013 01:55 922M *What operating system and graphics card?* gl-vendor:NVIDIA Corporation gl-version:3.3.0 gl-renderer:Quadro FX 1700M/PCIe/SSE2 gl-shading-language-version:3.30 NVIDIA via Cg compiler *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* Attachments: FG_2.12.0.PNG 62.0 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2013-10-17 11:38:04
|
Updates: Status: Accepted Comment #1 on issue 1192 by tom...@gmail.com: Menu: Debug --> Print Rendering Statistics --> Crash http://code.google.com/p/flightgear-bugs/issues/detail?id=1192 I can confirm this. Seems like osg is creating statistics for a crazy range of frames. If I just click "Print Rendering Statistics" after starting FlightGear osg tries to create statistics for framenumbers higher than 80k (which should be the number of frames after approx. 45 minutes) and forwards all of them to the new logging system which needs to allocate memory for each message and after a certain time fills up the whole memory, leading to the bad_alloc exception. I'm not sure if this is a problem with osg. I've found a message describing similar symptoms (http://osdir.com/ml/osg-users/2011-07/msg00194.html), but without any answer. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2014-01-02 22:18:33
|
Updates: Cc: zak...@ma... Comment #2 on issue 1192 by zak...@ma...: Menu: Debug --> Print Rendering Statistics --> Crash http://code.google.com/p/flightgear-bugs/issues/detail?id=1192 Maybe we should kill the menu option for the 3.0 release? I've personally never used it it I must admit, I always use the live on-screen statistics. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2014-01-03 10:34:43
|
Comment #3 on issue 1192 by jarl.arn...@gmail.com: Menu: Debug --> Print Rendering Statistics --> Crash http://code.google.com/p/flightgear-bugs/issues/detail?id=1192 I suggest at least limiting the statistics to last 10 seconds or 100 frames by default. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2014-01-03 10:46:25
|
Comment #4 on issue 1192 by zak...@ma...: Menu: Debug --> Print Rendering Statistics --> Crash http://code.google.com/p/flightgear-bugs/issues/detail?id=1192 Sure, but I'm not sure if the OSG API gives us that control or not - I guess we aren't deliberately requesting 80000 frames :) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2014-01-03 14:22:47
|
Comment #5 on issue 1192 by jarl.arn...@gmail.com: Menu: Debug --> Print Rendering Statistics --> Crash http://code.google.com/p/flightgear-bugs/issues/detail?id=1192 I've never used either. But then I'm no developer. I just came across this while testing the previous RC. Since it doesn't seem to work properly at all I guess it would be fair to disable it. Especially if there is at least one alternative way to view the same or simlar stats. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2014-01-04 20:05:25
|
Updates: Status: NeedInfo Comment #6 on issue 1192 by zak...@ma...: Menu: Debug --> Print Rendering Statistics --> Crash http://code.google.com/p/flightgear-bugs/issues/detail?id=1192 On my Ubuntu build, and Mac too, this seems to be a no-op, but doesn't crash. So I'm unsure what's going on here. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
Thanks for helping keep SourceForge clean.
X